Set enable_diagnostics="false" in your JGroups config file. Or pick a different diagnostics address / or port
Actually what you suggested is related to the error message
failed to join /126.96.36.199:7500 on en1: java.net.SocketException: Address already in use
But my main concern is about the two nodes with different partition names, that are in the same group, something it shouldn't happen unless there is something really wrong.
What I described, is happening with different nodes on different machines and with different nodes on the same machine AND different networks AND different operating systems (MacOs X and Windows)
So, what there is in common is just the jboss version (5.1.0.GA) and the 'all' instance, everything is different, but with the same result.
I'm puzzled, so do you have any idea?
Thanks a lot
Ah, I see...
Go to jboss-5.1.0/bin and run ./probe.sh -addr 188.8.131.52
It'll dump information about all instances. You'll see that instances do *not* cluster, except for the JBossMessaging cluster instances. Apparently JBM doesn't honor jboss.partition.name. I suggest ping the JBM folks for details...
Thanks for the help.
So, are you saying you're experiencing the same behavior on your environment also?
Yes, but only the JBM channels form a cluster, the others don't
That sounds like an issue that we have with the EAP.
There is a JIRA initiate by this https://jira.jboss.org/jira/browse/JBMESSAGING-1627
The workaround is to set
-g <partition name> -u <mcast address>
Ok then, for now we'll change the mcast address; not a big deal, just to be sure that we didn't mess up our configurations.
Thanks to all