-
Bug
-
Resolution: Done
-
Major
-
11.0.0.Alpha1
-
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.
- clones
-
JBEAP-10587 JGroups transport port_range should default to 0
- Closed