1 Reply Latest reply on Mar 25, 2010 4:16 PM by BJ Chippindale

    Problem isolating clusters

    Andreas Sander Newbie

      Hello,

       

      I have two JBoss 4.2.2 cluster and try to isolate them from each other. I tried to do it like written in this document:

      http://community.jboss.org/docs/DOC-12460

       

      Unfortunately, this does not work as expected.

      Changing group name and multicats group seems to be easy, but changing the multicast port is a problem.

      The document states, that "jboss.hapartition.mcast_port" has to be changed in "cluster-service.xml". Unfortunately neither the jboss.hapartition.mcast_port variable nor the file cluster-service.xml exists. Same for "jboss.webpartition.mcast_port" and "jboss-web-cluster.sar"

       

      From the different XML files, I assumed that following startup settings could work:

      -Djboss.partition.name=MySecondCluster
      -Djboss.partition.udpGroup=228.1.2.4
      -Djboss.partition.udpPort=55544

      Now the cluster do not see each other, but "MySecondCluster" does not work. I always get warnings like this:

       

      2010-03-08 08:26:34,781 WARN  [org.jgroups.protocols.UDP] discarded message from different group "MySecondCluster" (our group is "Tomcat-MySecondCluster"). Sender was 192.168.1.41:3000
      2010-03-08 08:26:35,328 WARN  [org.jgroups.protocols.UDP] discarded message from different group "Tomcat-MySecondCluster" (our group is "MySecondCluster"). Sender was 192.168.1.41:2995
      2010-03-08 08:26:37,375 WARN  [org.jgroups.protocols.UDP] discarded message from different group "MySecondCluster-SFSBCache" (our group is "MySecondCluster"). Sender was 192.168.1.41:3004
      2010-03-08 08:26:39,609 WARN  [org.jgroups.protocols.UDP] discarded message from different group "MySecondCluster-EntityCache" (our group is "MySecondCluster"). Sender was 192.168.1.41:3008
      2010-03-08 08:26:55,968 WARN  [org.jgroups.protocols.UDP] discarded message from different group "MessagingPostOffice" (our group is "MySecondCluster"). Sender was 192.168.1.41:3018

      It seems for me, that the components of the second cluster do not see each other. 192.168.1.41 is the IP of the second cluster.

       

      Any help would be appreciated.

       

      Andreas