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

socket-binding/jgroups-tcp client mappings do not map to jgroups.external_addr properly

    Details

    • Steps to Reproduce:
      Hide

      To reproduce:

      1. /socket-binding-group=standard-sockets/socket-binding=jgroups-tcp:write-attribute(\
          name=client-mappings, value=[{ \
            "destination-address" => "${env.JGROUPS_NAME:external.host.zzz}", \
            "destination-port" => "${env.JGROUPS_PORT:7600}" }\
          ])
        
      2. If using S3_PING, look at the *.list file, and you'll find that wildfly is still advertising the IP address bound to the default private interface.
      Show
      To reproduce: /socket-binding-group=standard-sockets/socket-binding=jgroups-tcp:write-attribute(\ name=client-mappings, value=[{ \ "destination-address" => "${env.JGROUPS_NAME:external.host.zzz}" , \ "destination-port" => "${env.JGROUPS_PORT:7600}" }\ ]) If using S3_PING , look at the *.list file, and you'll find that wildfly is still advertising the IP address bound to the default private interface.
    • Workaround Description:
      Hide

      The workaround is to pass in the required external address via the jgroups.external_addr system property:

      option 1
        /system-property=jgroups.external_addr:add(value=${env.JGROUPS_NAME:external.host.zzz})
      
      option 2
      standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 -bprivate 0.0.0.0 -Djgroups.external_addr=external.host.zzz
      
      Show
      The workaround is to pass in the required external address via the jgroups.external_addr system property: option 1 /system-property=jgroups.external_addr:add(value=${env.JGROUPS_NAME:external.host.zzz}) option 2 standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 -bprivate 0.0.0.0 -Djgroups.external_addr=external.host.zzz

      Description

      socket-binding/jgroups-tcp client mappings do not map to the system property jgroups.external_addr correctly, and therefore jgroups ALWAYS advertises the address bound to the private interface.

      When setting the client mappings for the jgroups-tcp socket binding, wildfly should ensure that the pingdata for various discovery protocols announces the destination address set there, presumably by setting the jgroups.external_addr value.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                pferraro Paul Ferraro
                Reporter:
                rbellamy G. Richard Bellamy
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: