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

[Miroslav Novak (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548202#comment-13548202 ] 

Miroslav Novak commented on WFLY-10046:
---------------------------------------

[~pferraro] Thanks! This is it. I was looking why we had such config in our tests and purpose was to disconnect JGroups cluster with 2 nodes. It served well the intention until now but as you've pointed out this config does not make sense. 

I plan to change the config in this way, does it looks ok from you pov:
{code}
             <stack name="udp">
		    <transport type="TUNNEL" shared="false" socket-binding="jgroups-udp" >
		       <property name="gossip_router_hosts">127.0.0.1[12001]</property>
		    </transport>
                    <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"/>                    
                </stack>
{code}

> Cannot create cluster with JGroups Gossip 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
>         Attachments: standalone-full-ha-gosship1.xml, standalone-full-ha-gosship2.xml
>
>
> I've used config from EAP 7.1.0/WF11 where gossip 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}
> Gossip 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)