3 Replies Latest reply on Feb 8, 2014 4:09 AM by Rituraj Sinha

    clustering issues while migrating  from 7.1.3 to 7.2.0

    Rituraj Sinha Novice

      we have been able to do clustering on the server-group level (domain configuration) on ha-profile in jboss7.1.3 but we are facing issues while doing the same on jboss7.2.0


      on jboss7.1.3

      we have created 2 server groups with one application-server/node each and deployed 2 different war files on each of them after the deployment  we were able to see something below in the logs



      [Server:devops301pw1] 04:40:48,905 INFO  [stdout] (ServerService Thread Pool -- 55) GMS: address=devops301p_dc:devops301pw1/devops-cluster1, cluster=devops-cluster1, physical address=X.X.X.X:7700

      [Server:devops301pw2] 04:40:49,593 INFO  [stdout] (ServerService Thread Pool -- 53) GMS: address=devops301p_dc:devops301pw2/devops-cluster2, cluster=devops-cluster2, physical address=X.X.X.X:7800


      by this way we were able to separate the clusters running on the same ha profile ...otherwise all the members running on ha profile were coming into the same cluster which we don't want

      to achieve this we have done some changes in domain.xml as below

      1) passed system properties on the server-group level

      for server-group 1


                      <property name="jboss.cluster.group.name" value="devops-cluster1"/>



      for server-group2


                      <property name="jboss.cluster.group.name" value="devops-cluster2"/>



      [Server:devops301pw2] 04:40:59,966 INFO  [org.jboss.as.clustering] (MSC service thread 1-2) JBAS010238: Number of cluster members: 1

      [Server:devops301pw1] 04:40:59,293 INFO  [org.jboss.as.clustering] (MSC service thread 1-1) JBAS010238: Number of cluster members: 1

      now "jboss.cluster.group.name" is passed as in ha profile


         2)         <cache-container name="web" aliases="standard-session-cache" default-cache="repl" module="org.jboss.as.clustering.web.infinispan">
                      <transport cluster="${jboss.cluster.group.name}" lock-timeout="60000"/>
                      <replicated-cache name="repl" mode="ASYNC" batching="true">

      we are doing the same configuration but we are not able to separate the clusters on the server-group level in jboss7.2.0 and getting the below message


      [Server:wildfly-consumer-devops304pw1] 22:26:19,225 INFO  [stdout] (ServerService Thread Pool -- 64) GMS: address=wildfly-devops304p_dc:wildfly-consumer-devops304pw1/wildfly-consumer-cluster, cluster=web, physical address=X.X.X.X:7700


      [Server:wildfly-vertical-devops304pw1] 22:26:06,852 INFO  [stdout] (ServerService Thread Pool -- 53) GMS: address=wildfly-devops304p_dc:wildfly-vertical-devops304pw1/wildfly-vertical-cluster, cluster=web, physical address=X.X.X.X:7800


      [Server:wildfly-consumer-devops304pw1] 22:26:19,997 INFO  [org.jboss.as.clustering] (MSC service thread 1-2) JBAS010238: Number of cluster members: 2



      more information:

      b) tcp stack is being used in both configuration


      the only difference between the 2 env is jdk version in the previous configuration we were using jdk1.6 and the later we are using 1.7


      let me know if any other detail is required ....we have been stuck in this issue from some time please help me to resolve this ...