Ugly behavior with default-interface and mod_cluster
sewatech Aug 15, 2014 4:05 PMHi,
I’m trying to setting a cluster of WildFly 8.1.0.Final, with mod_cluster as a front end, and all of this in docker containers. I’ve customized the network configuration of my WildFly, in the standalone-ha.xml. I have 2 interfaces : all and public :
<interfaces> <interface name="public"> <nic name="eth0"/> </interface> <interface name="all"> <any-address/> </interface> </interfaces>
I have explicitly declared the interface of all my socket-bindings :
<socket-binding name="management-http" port="${jboss.management.http.port:9990}" interface="public" /> <socket-binding name="management-https" port="${jboss.management.https.port:9993}" interface="public" /> <socket-binding name="ajp" port="${jboss.ajp.port:8009}" interface="public"/> <socket-binding name="http" port="${jboss.http.port:8080}" interface="public"/> <socket-binding name="https" port="${jboss.https.port:8443}" interface="public"/> <socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700" interface="public"/> <socket-binding name="jgroups-tcp" port="7600" interface="public"/> <socket-binding name="jgroups-tcp-fd" port="57600" interface="public"/> <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688" interface="public"/> <socket-binding name="jgroups-udp-fd" port="54200" interface="public"/> <socket-binding name="modcluster" port="0" multicast-address="224.0.1.105" multicast-port="23364" interface="public"/> <socket-binding name="txn-recovery-environment" port="4712" interface="public"/> <socket-binding name="txn-status-manager" port="4713" interface="public"/>
Now, when I declare the default-interface to all, mod_cluster can discover my instance.
<socket-binding-group name="standard-sockets" default-interface="all" port-offset="${jboss.socket.binding.port-offset:0} »>
But if I declare the default interface to public, mod_cluster cannot discover my instance.
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
I thought that the default-interface attribute was the default value for the interface attribute of all the socket-bindings. So why does it has an impact whereas I've declare the interface on all the socket-bindings ?
Alexis