Wildfly 10 HA Clustering On AWS Does not work

Question

I am trying to set up an HA Clustering on Amazon Web Service with Wildfly-10. My standalone-ha.xml configuration is

...
<subsystem xmlns="urn:jboss:domain:jgroups:4.0">
<channels default="ee">
    <channel name="ee" stack="s3ping"/>
<channels>
<stacks>
       ...            
    <stack name="s3ping">
       <transport type="TCP" socket-binding="jgroups-tcp" diagnostics-socket-binding="jgroups-diagnostics"/>
           <protocol type="S3_PING">
               <property name="access_key">
                   <%= @s3_access_key %>
               </property>
               <property name="secret_access_key">
                   <%= @s3_secret_access_key %>
               </property>
               <property name="prefix">
                   <%= @s3_bucket %>
               </property>
               <property name="timeout">
                   60000
               </property>
           </protocol>
           <protocol type="MERGE2"/>
           <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>              
           <protocol type="FD"/>
           <protocol type="VERIFY_SUSPECT"/>
           <protocol type="BARRIER"/>
           <protocol type="pbcast.NAKACK"/>
           <protocol type="UNICAST2"/>
           <protocol type="pbcast.STABLE"/>
           <protocol type="pbcast.GMS"/>
           <protocol type="UFC"/>
           <protocol type="MFC"/>
           <protocol type="FRAG2"/>
       </stack>
</stacks>
</subsystem>
...

With very similar configuration I am able to cluster with Wildfly 8 and Wildfly 8.2. But with Wildfly 10, I am not able to succeed it.

Also I have added <distributable/> to my web.xml.

On console I am getting a warn saying;

[org.jboss.protocols.pbcast.GMS] (MSC service thread 1-1) node1: JOIN(node1) sent to node1 timed out (after 3000 ms), on try 1

and it continues up to on try 10.

What is my fault and how can I fix it.

Thanks.

score 0 · Accepted Answer · answered Jun 13 '16 at 13:07

I have found the reason of warning. Two machines can not reach each other. I am sharing the relevant part;

<interfaces>
    <interface name="management">
        <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
    </interface>
    <interface name="public">
        <inet-address value="${jboss.bind.address:127.0.0.1}"/>
    </interface>
    <interface name="private">
        <inet-address value="${jboss.bind.address.private:127.0.0.1}"/>
    </interface>
</interfaces>
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
    <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
    <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
    <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
    <socket-binding name="http" port="${jboss.http.port:8080}"/>
    <socket-binding name="https" port="${jboss.https.port:8443}"/>
    <socket-binding name="jgroups-mping" interface="private" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/>
    <socket-binding name="jgroups-tcp" interface="public" port="7600"/>
    <socket-binding name="jgroups-tcp-fd" interface="public" port="57600"/>
    <socket-binding name="jgroups-udp" interface="private" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688"/>
    <socket-binding name="jgroups-udp-fd" interface="private" port="54200"/>
    <socket-binding name="modcluster" port="0" multicast-address="224.0.1.105" multicast-port="23364"/>
    <socket-binding name="txn-recovery-environment" port="4712"/>
    <socket-binding name="txn-status-manager" port="4713"/>
    <outbound-socket-binding name="mail-smtp">
        <remote-destination host="localhost" port="25"/>
    </outbound-socket-binding>
</socket-binding-group>

Wildfly 10 HA Clustering On AWS Does not work

1 Answers1