[jboss-jira] [JBoss JIRA] (WFLY-11913) JGroups client sockets are not registered with the socket binding manager
Paul Ferraro (Jira)
issues at jboss.org
Wed Mar 27 19:08:00 EDT 2019
Paul Ferraro created WFLY-11913:
-----------------------------------
Summary: JGroups client sockets are not registered with the socket binding manager
Key: WFLY-11913
URL: https://issues.jboss.org/browse/WFLY-11913
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 16.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list