[jboss-jira] [JBoss JIRA] (WFLY-8891) Cluster deployment is not happening with wildfly 10

[Subash singh (JIRA)]

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

Subash singh commented on WFLY-8891:
------------------------------------

Hi Radoslav,

Thanks for quick response on this.
I have checked on my vm multicast is enabled for eth0 and eth1 but not for lo. 

when i check it by executing below cmd found that cluster id is using lo interface.
{color:#f6c342}# netstat -g
IPv6/IPv4 Group Memberships
Interface       RefCnt Group
--------------- ------ ---------------------
lo              1      225.9.9.25
lo              1      all-systems.mcast.net
eth0            1      ntds1r.mcast.net
eth0            1      all-systems.mcast.net
eth1            1      all-systems.mcast.net
lo              1      ff02::1
eth0            1      ff02::202
eth0            1      ff02::1:ffb9:a7dd
eth0            1      ff02::1
eth1            1      ff02::202
{color}

my cluster setup is not working because it is using *lo * interface and for *lo* multicast is not enable?
can you suggest how to proceed further.

Thanks
Subash Singh



> Cluster deployment is not happening with wildfly 10
> ---------------------------------------------------
>
>                 Key: WFLY-8891
>                 URL: https://issues.jboss.org/browse/WFLY-8891
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.Final
>         Environment: OS - rhel- 6.7
> JRE - openjdk 1.8
> Keycloak-3.0.0
>            Reporter: Subash singh
>            Assignee: Paul Ferraro
>            Priority: Critical
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> When we reviewed the logs of the second instance, we saw:
> 2017-06-05 14:33:05,123 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000078: Starting JGroups channel web
> 2017-06-05 14:33:05,123 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000078: Starting JGroups channel keycloak
> 2017-06-05 14:33:05,123 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000078: Starting JGroups channel server
> 2017-06-05 14:33:05,123 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000078: Starting JGroups channel ejb
> 2017-06-05 14:33:05,123 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000078: Starting JGroups channel hibernate
> Received new cluster view for channel keycloak:* [keycloak02|0] (1) [keycloak02]*
> 2017-06-05 14:33:05,148 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000094: Received new cluster view for channel hibernate: [keycloak02|0] (1) [keycloak02]
> 2017-06-05 14:33:05,149 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000094: Received new cluster view for channel ejb: [keycloak02|0] (1) [keycloak02]
> 2017-06-05 14:33:05,149 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000094: Received new cluster view for channel server: [keycloak02|0] (1) [keycloak02]
> 2017-06-05 14:33:05,149 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000094: Received new cluster view for channel web: [keycloak02|0] (1) [keycloak02]
> both nodes are not joining the cluster.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)