Launch the Cluster with Nodes on a Single Non-MultiHomed Machine
Scenario 2: Two Nodes on a Single, Non-Multihomed, Machine Running multiple nodes on a single machine that only has a single IP address is a common scenario in a development environment. You need to be sure each server instance has its own work area. One way to do this is to simply make copies of the all configuration. For example, assuming the root of the JBoss distribution was unzipped to /var/jboss, you could: $ cd /var/jboss/server $ cp -r all node1 $ cp -r all node2 Two processes can’t bind sockets to the same address and port, so we’ll have to tell JBoss to use different ports for the two instances. This can be done by setting the jboss.service. binding.set system property. To launch the first instance, open a console window and: $ ./run.sh -c node1 -b 192.168.0.101 -Djboss.messaging.ServerPeerID=1 \ -Djboss.service.binding.set=ports-default For the second instance, in a second console window: $ ./run.sh -c node2 -b 192.168.0.101 -Djboss.messaging.ServerPeerID=2 \ -Djboss.service.binding.set=ports-01 This tells the ServiceBindingManager on the first node to use the standard set of ports (e.g. JNDI on 1099). The second node uses the “ports-01” binding set, with which by default each port has an offset of 100 from the standard port number (e.g. JNDI on 1199).