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

JGroups transport port_range should default to 0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 11.0.0.Beta1
    • 11.0.0.Alpha1
    • Clustering
    • 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.

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: