[jboss-jira] [JBoss JIRA] (WFLY-10046) Cannot create cluster with JGroups Gosship router

Miroslav Novak (JIRA) issues at jboss.org
Mon Mar 19 07:06:00 EDT 2018


     [ https://issues.jboss.org/browse/WFLY-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Miroslav Novak updated WFLY-10046:
----------------------------------
    Steps to Reproduce: 
* Unzip WF12 to two different directories
* Download attached standalone xml files and copy instead of standalone-full-ha.xml
* Start gosship router by: {{java -cp $JBOSS_HOME//bin/client/jboss-client.jar  org.jgroups.stack.GossipRouter -port 12001 -bindaddress 0.0.0.0}}
* Start first by: {{sh standalone.sh -c standalone-full-ha.xml}}
* Start second by: {{sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000}}

There should appear message like: {code}
11:56:17,607 INFO  [org.apache.activemq.artemis.core.server] (Thread-9 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3 at 49be2674)) AMQ221027: Bridge ClusterConnectionBridge at 6a0e45dc [name=sf.my-cluster.3c2415d7-2b61-11e8-81e5-f496342f6705, queue=QueueImpl[name=sf.my-cluster.3c2415d7-2b61-11e8-81e5-f496342f6705, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUUID=3edb46eb-2b61-11e8-86e1-54e1ad305985]]@87f9619 targetConnector=ServerLocatorImpl (identity=(Cluster-connection-bridge::ClusterConnectionBridge at 6a0e45dc [name=sf.my-cluster.3c2415d7-2b61-11e8-81e5-f496342f6705, queue=QueueImpl[name=sf.my-cluster.3c2415d7-2b61-11e8-81e5-f496342f6705, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUUID=3edb46eb-2b61-11e8-86e1-54e1ad305985]]@87f9619 targetConnector=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost], discoveryGroupConfiguration=null]]::ClusterConnectionImpl at 1691717715[nodeUUID=3edb46eb-2b61-11e8-86e1-54e1ad305985, connector=TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=8080&host=localhost, address=jms, server=ActiveMQServerImpl::serverUUID=3edb46eb-2b61-11e8-86e1-54e1ad305985])) [initialConnectors=[TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost], discoveryGroupConfiguration=null]] is connected
{code}
which informs that Artemis cluster was formed but it does not. 

  was:
* Unzip WF12 to two different directories
* Download attached standalone xml files and copy instead of standalone-full-ha.xml
* Start gosship router by: {{java -cp $JBOSS_HOME//bin/client/jboss-client.jar  org.jgroups.stack.GossipRouter -port 12001 -bindaddress 0.0.0.0}}
* Start first by: {{sh standalone.sh -c standalone-full-ha.xml}}
* Start second by: {{sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000}}



> Cannot create cluster with JGroups Gosship router
> -------------------------------------------------
>
>                 Key: WFLY-10046
>                 URL: https://issues.jboss.org/browse/WFLY-10046
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 12.0.0.Final
>            Reporter: Miroslav Novak
>            Assignee: Paul Ferraro
>            Priority: Blocker
>         Attachments: standalone-full-ha-gosship1.xml, standalone-full-ha-gosship2.xml
>
>
> I've used config from EAP 7.1.0/WF11 where gosship router was configured in udp stack like:
> {code}
>   <stack name="udp">
>                     <transport type="UDP" shared="false" socket-binding="jgroups-udp"/>
>                     <protocol type="PING"/>
>                     <protocol type="MERGE3"/>
>                     <protocol type="FD_SOCK"/>
>                     <protocol type="FD_ALL"/>
>                     <protocol type="VERIFY_SUSPECT"/>
>                     <protocol type="pbcast.NAKACK2"/>
>                     <protocol type="UNICAST3"/>
>                     <protocol type="pbcast.STABLE"/>
>                     <protocol type="pbcast.GMS"/>
>                     <protocol type="UFC"/>
>                     <protocol type="MFC"/>
>                     <protocol type="FRAG2"/>
>                     <protocol type="TUNNEL">
>                         <property name="gossip_router_hosts">
>                             0.0.0.0[12001]
>                         </property>
>                     </protocol>
>                 </stack>
> {code}
> Gosshop router was started on localhost:
> {{java -cp $JBOSS_HOME//bin/client/jboss-client.jar  org.jgroups.stack.GossipRouter -port 12001 -bindaddress 0.0.0.0}}
> but cluster does not form up. The same configuration works in EAP 7.1.
> Attaching xml config files for both of the servers.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)



More information about the jboss-jira mailing list