2015-11-04 76 views
2

我试图在EC2的HA谱运行WildFly 10,但我得到了以下错误:WildFly 10的JGroups和EC2

05:03:28,308 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=jgroups/stack=tcp/protocol=FD_SOCK' are not available: 
[Server:server-one]  org.wildfly.network.socket-binding.jgroups-tcp-fd; There are no known registration points which can provide this capability. 
[Server:server-one] 05:03:28,310 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=jgroups/stack=tcp/transport=TCP' are not available: 
[Server:server-one]  org.wildfly.network.socket-binding.jgroups-tcp; There are no known registration points which can provide this capability. 

我JGroups的配置看起来像这样

<subsystem xmlns="urn:jboss:domain:jgroups:4.0"> 
       <channels default="ee"> 
        <channel name="ee" stack="tcp"/> 
       </channels> 
       <stacks> 
      <stack name="tcp"> 
       <transport type="TCP" socket-binding="jgroups-tcp"/> 
       <protocol type="S3_PING"> 
        <property name="access_key">accesskey</property> 
        <property name="secret_access_key">secretkey</property> 
        <property name="location">bucketname</property> 
       </protocol> 
       <protocol type="MERGE3"/> 
       <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> 
       <protocol type="FD"/> 
       <protocol type="VERIFY_SUSPECT"/> 
       <protocol type="pbcast.NAKACK2"> 
        <property name="use_mcast_xmit">false</property> 
        <property name="use_mcast_xmit_req">false</property> 
       </protocol> 
       <protocol type="UNICAST3"/> 
       <protocol type="pbcast.STABLE"/> 
       <protocol type="pbcast.GMS"/> 
       <protocol type="MFC"/> 
       <protocol type="FRAG2"/> 
       <protocol type="RSVP"/> 
      </stack> 
     </stacks> 
</subsystem> 

有没有人知道There are no known registration points which can provide this capability是什么意思?

+0

你刚刚改变了tcp堆栈吗?你应该添加一个新的s3ping堆栈而不是tcp –

回答

3

原来,我混淆了我的套接字绑定。我用的是HA协议的全-HA-插座插座结合,就像这样:

<server-groups> 
     <server-group name="main-server-group" profile="ha"> 
      <jvm name="default"> 
       <heap size="64m" max-size="512m"/> 
      </jvm> 
      <socket-binding-group ref="full-ha-sockets"/> <!-- THIS IS BROKEN --> 
      <deployments> 
       <deployment name="activemq-rar" runtime-name="activemq-rar"/> 
       <deployment name="hawtio.war" runtime-name="hawtio.war"/> 
      </deployments> 
     </server-group> 
     <server-group name="other-server-group" profile="full-ha"> 
      <jvm name="default"> 
       <heap size="64m" max-size="512m"/> 
      </jvm> 
      <socket-binding-group ref="full-ha-sockets"/> 
     </server-group> 
    </server-groups> 

一旦我有固定的插座绑定,错误走了:

<server-groups> 
     <server-group name="main-server-group" profile="ha"> 
      <jvm name="default"> 
       <heap size="64m" max-size="512m"/> 
      </jvm> 
      <socket-binding-group ref="ha-sockets"/> <!-- THIS IS FIXED --> 
      <deployments> 
       <deployment name="activemq-rar" runtime-name="activemq-rar"/> 
       <deployment name="hawtio.war" runtime-name="hawtio.war"/> 
      </deployments> 
     </server-group> 
     <server-group name="other-server-group" profile="full-ha"> 
      <jvm name="default"> 
       <heap size="64m" max-size="512m"/> 
      </jvm> 
      <socket-binding-group ref="full-ha-sockets"/> 
     </server-group> 
    </server-groups> 
+0

这是为'domain.xml'文件提供的同样的错误,我用'standalone-ha.xml'得到了什么应该是'stand-in'中服务器组的替代品-full-ha.xml'因为按照我的场景我必须使用'standalone-ha.xml'进行集群。 –

0

我有一个类似也是问题。但是,而不是在<server-group />中的问题,我的问题是在我的主机。

我创建了一个初始主机,以便在已存在的服务器组中使用配置文件full-hafull-ha-sockets。之后,我使用配置文件haha-sockets创建一个新的服务器组,并将此主机移动到这个新的服务器组。

问题?我的主机使用配置文件ha,但使用full-ha-sockets而不是ha-sockets。我做了一个安装使用远程只使用ha-sockets EJB,并有当我试图来调用EJB远程方法的远程出站连接同样的错误:

There are no known registration points which can provide this capability 

我在想,我的主人是使用ha-sockets。所以,我让主机使用ha-sockets并且错误消失了。我失去了很多时间去发现这个错误。