Uploaded image for project: 'mod_cluster'
  1. mod_cluster

mod_cluster UDP multicast listener does not honour the proper interface


    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 1.3.1.Final
    • Core + SPIs
    • None

      Wrong interface

      On a multi-interface systems, it is necessary to pick the right interface the balancer should send to
      and worker should receive from. Merely setting UDP multicast address and port is not enough.

      • With Apache HTTP Server, this is achieved by AdvertiseBindAddress directive (though the default is wrong MODCLUSTER-487)
      • With Undertow mod_cluster proxy in Wildfly, the interface could be set in socket bindings, e.g.:
        <socket-binding name="modcluster-adv" port="7637" multicast-address="" multicast-port="7637" interface="special-public"/>
      • In the case of Tomcat/JBossWeb, historical mod_cluster 1.x documentation suggests that it is done "automatically": interface on which mod_cluster's internal connection was established.

      The statement from the historical documentation doesn't make much sense to me – which internal connection?

      The actual result is that if you have 2 boxes, 2 interfaces each:

      Balancer (Undertow or Apache HTTP Server)

      Box 1: enp1s0:, enp2s0:, all connectors including advertisement bound to enp2s0:

      Worker (Tomcat)

      Box 2: enp1s0:, enp2s0:, HTTP/AJP connectors bound to enp2s0:

      <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" advertise="true"
                loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2"
                stickySession="true" stickySessionForce="false" stickySessionRemove="true"
                autoEnableContexts="true" advertiseGroupAddress="" advertisePort="7637"
      <Connector address="" port="8080" protocol="HTTP/1.1" 
                 redirectPort="8443" />
      <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" address=""/>
      <Engine name="Catalina" defaultHost="localhost" jvmRoute="">

      The worker node is unable to receive balancer's advertising. The tomcat actually listens for advertisements on enp1s0:, because if I rebind the balancer to enp1s0:, the whole setup suddenly works. I also verified it with the Advertize.java utility.


      IMHO, we have to either make it configurable via listener's attribute or fetch the interface from one of the available connectors (sometimes AJP is not configured, sometimes HTTP(S) ain't – but at least one is always present).

            rhn-engineering-rhusar Radoslav Husar
            mbabacek1@redhat.com Michal Karm
            Michal Karm Michal Karm
            Jean-Frederic Clere
            0 Vote for this issue
            3 Start watching this issue