amazon web services - Wildfly 10 HA Clustering On AWS Does not work -
i trying set ha clustering on amazon web service wildfly-10. 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 similar configuration able cluster wildfly 8 , wildfly 8.2. wildfly 10, not able succeed it.
also have added <distributable/> web.xml.
on console getting warn saying;
[org.jboss.protocols.pbcast.gms] (msc service thread 1-1) node1: join(node1) sent node1 timed out (after 3000 ms), on try 1 and continues on try 10.
what fault , how can fix it.
thanks.
i have found reason of warning. 2 machines can not reach each other. sharing 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>
Comments
Post a Comment