[
https://issues.jboss.org/browse/WFLY-8657?page=com.atlassian.jira.plugin....
]
Paul Ferraro moved JBEAP-10588 to WFLY-8657:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8657 (was: JBEAP-10588)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR17)
JGroups transport port_range should default to 0
------------------------------------------------
Key: WFLY-8657
URL:
https://issues.jboss.org/browse/WFLY-8657
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 11.0.0.Alpha1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Because we configure our JGroups transport via a socket-binding, we already leverage the
port-offset feature to mitigate port conflicts - thus removing the need to rely on the
port_range property. The use of port_range is troublesome from a management perspective,
as it means that the actual port can differ from the ports reported by the management
layer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)