Isolate JBoss clusters running on the same network
https://access.redhat.com/kb/docs/DOC-34950 Isolating JBoss clusters running on the same network Article ID: 34950 - Created on: Oct 1, 2009 7:18 AM - Last Modified: Mar 28, 2011 11:24 AM Issue What config changes are required to isolate clusters on the same network? I need to start JBoss so it doesn't join an existing cluster. Is there a way that the clusters can be segregated in JBoss from seeing the incorrect nodes? Is there configuration in Jboss that will specify the nodes that are in the cluster? Environment JBoss Enterprise Application Platform (EAP) 5.x 4.x JBoss Enterprise SOA Platform 4.3 Sun Linux HPUX Resolution http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3/html/Server_Configuration_Guide/ch13s03.html http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/Administration_And_Configuration_Guide/cl ustering-jgroups-isolation.html Specify a unique partition name (-g) and multicast address (-u) for each cluster: ./run.sh -u 230.1.1.1 -g QAPartition00 ... On some operating systems (such as Linux with EAP 4.2 CP05, EAP 4.3 CP03, and SOA-P 4.3 CP01 or older), the following properties also need to be set: to unique ports for each cluster channel -Djboss.messaging.controlchanneludpport= -Djboss.messaging.datachanneludpport= -Djboss.hapartition.mcast_port= -Djboss.webpartition.mcast_port= -Djboss.ejb3entitypartition.mcast_port= -Djboss.ejb3sfsbpartition.mcast_port= N.B If using TCP for all cluster channels, including messaging, then only the -g option is required to isolate clusters Tags: kcs_verified, soap, eap, jgroups, isolation, cluster, jboss, kcs