Generally your nodes are on different hosts, in which case you would not get port conflicts.
Possibly, you could have multiple IP addresses and pass in the -b option to the run script specifying a different ip for each host, but depending on the actual network setup, the two instances may not see each other.
I would assume you are doing this as a test? As having 2 cluster nodes on one host kind of defeats the purpose of a highly available cluster.
That or maybe you are just trying to handle the extreme edge case of the JVM crashing.
Yes you make very good points. When I started to try clustering my servers I thought running a cluster on one machine would be easier for testing/learning, but now I know otherwise. Now that I am trying the clustering with two machines there are no more port issues (though unfortunately there are others). Basic clustering appears to be dead simple to configure with JBoss 3.2.5 (nice work), but getting something like singletons to work with a cluster is another story -- at least I am still stumped (see other posts in this forum).
Thanks for your reply.
You can run two instances of JBoss with the "all" configuration on a single machine with minimal config changes. JBoss provides the ServiceBindingManager facility to run multiple instances on the same box.
lists many different articles on Clustering
describes setting up multiple instances on the same box.
Please try to look at the wiki. All your answers are usually answered there. Also if you have something new to tell the world, you are free to place it on the wiki.