2015-11-04 38 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並且錯誤消失了。我失去了很多時間去發現這個錯誤。