AWS上的Wildfly 10 HA群集不起作用

我正尝试在Amazon Web Service上使用Wildfly-10设置HA群集。我的standalone-ha.xml配置是AWS上的Wildfly 10 HA群集不起作用

... 
<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> 
...

使用非常类似的配置，我可以使用Wildfly 8和Wildfly 8.2进行群集。但对于Wildfly 10，我无法取得成功。

此外我还添加了<distributable/>到我的web.xml。

在控制台上，我收到了警告;

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

并且它继续高达on try 10。

什么是我的错，我该如何解决它。

谢谢。

来源

2016-06-09 xxlali

我发现了警告的原因。两台机器无法到达对方。我正在分享相关部分;

<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>

来源

2016-06-13 13:07:07 xxlali

AWS上的Wildfly 10 HA群集不起作用

回答

相关问题