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

<socket-protocol> ignores port-offset

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 27.0.0.Final
    • None
    • Clustering
    • None
    • Hide

      Start EAP with a port-offset configured and anything that triggers clustering to start (such as deploying a <distributable/> web application.

      Check ports in netstat, and observe that the FD_SOCK port does not apply the offset.

      Show
      Start EAP with a port-offset configured and anything that triggers clustering to start (such as deploying a <distributable/> web application. Check ports in netstat, and observe that the FD_SOCK port does not apply the offset.
    • Release Notes
    • Hide

      Manually configure the exact port in the socket-bindings.  Also add fixed-port=true so the config won't change when the bug gets fixed.

              <socket-binding name="jgroups-udp-fd" interface="private" port="1234" fixed-port="true"/>

      Show
      Manually configure the exact port in the socket-bindings.  Also add fixed-port=true so the config won't change when the bug gets fixed.         <socket-binding name="jgroups-udp-fd" interface="private" port="1234" fixed-port="true"/>
    • ---
    • ---

      The JGroups subsystem <socket-protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> ignores the port offset on the socket-binding, and therefore uses the wrong port.

       

              rchakrab Ranabir Chakraborty
              rchakrab Ranabir Chakraborty
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: