-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR17
-
None
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.
- is cloned by
-
-
- Closed
-
- relates to
-
JBEAP-11195 DR19 Cluster behaves differently when trying to use already used IP/port for "jgroups-udp" socket-binding
-
- Closed
-