Just to add further details. The other instances that are showing up DO have their respective .xml files configured with ip_mcast="false" as well.
We are on a private development subnet and use the same jboss app server configuration from our own internal cvs server. So all jboss application server configurations on the subnet are the same.
ip_mcast=false means that instead of sending 1 multicast msg to N members, we send N datagrams (one per member).
If you want to turn off clustering, comment ClusterPartition in cluster-service.xml
This may be a problem for me then.
We want to support just one deployment in the all configuration (which includes session, and entity beans which are configured to be clustered in their descriptors and thus bound to HAPartition) but for standard usage we want to basically limit the cluster size to 1(as most people will not wish to use the clustering capability).
We were hoping to find a simple descriptor attribute or the like that would essentially toggle the clustering capability on(Unlimited cluster size) or off(limit to a cluster of 1) but not have to change how the ejbs are deployed.
If I comment out default partition I have to redeploy my ejbs with new descriptors as their dependancy on DefaultPartition will fail :(
Maybe we will have to have two different deployments after all (one based on the "all" configuration and one based on "default")
Can I set mcast to true but then just set the bind address to 127.0.0.1?
Would that limit me to a cluster of exactly 1? :)
Yes, that works
Another possibility is to set ip_ttl=1