This is the change to ConfiguringMultipleJBossInstancesOnOneMachine that I am asking about: Difference between version 34 and version 33: Line 45 was replaced by lines 45-46 - If you intend to launch multiple JBoss instances on the same machine and have them form a cluster, you might write some kind of script to launch the two instances. It is a good practice to add some kind of pause in your script between the launch of the first instance and the second. 10 to 20 seconds is good. + We highly recommend against configurating a cluster using the Service Binding Manager. Instead bind each server instance to a separate ip address (or DNS alias) (bound to the same NIC or not):\\ + __ e.g. $run.sh -c node1 -b 192.168.4.1 (or -b node1.mycluster.acme.com) Removed line 47 - This is because if both instances are launched simultaneously, they both may decide they are the JGroups coordinator. At this point, you will have two independent clusters of one node each. If this happens, both nodes may begin to start HASingleton services, such as HA-JMS. A few seconds later, the two nodes will discover each other and the two clusters will merge. One of the nodes will no longer be coordinator, and the HASingleton services will be stopped. Stopping a service that's in the middle of starting does not always go cleanly. Removed line 49 - By putting a pause in your startup script, it gives the first node a chance to become coordinator before the second node starts. The second node will then cleanly join the cluster, and no HASingleton services will be started on it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996094#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...