Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11913

JGroups client sockets are not registered with the socket binding manager

    Details

      Description

      Because the JGroups subsystem does not expose a socket-binding for client sockets, these sockets are not registered with the socket binding manager.
      Currently, TCP, TCP_NIO2, FD_SOCK use the same bind address for server vs client sockets and use a random ephemeral port for configuring the client socket. For environment with strict networking rules, this is not ideal, and requires overriding adhoc JGroups properties. Unfortunately, overriding the client_bind_port in this way does not recognize the port-offset of the associated socket binding group.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pferraro Paul Ferraro
                  Reporter:
                  pferraro Paul Ferraro
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: