1 of 1 people found this helpful
I've had some strange behaviour. It was a network missconfiguration (maybe on the fly).
I experiment a little with the jgroups test program and figure out that it is a difference (in my case) which ip address is bound (run.sh -b) and which multicast address is used.
Maybe it helps in your case.
Well, we have been unable to reproduce up to this point.
I will definitely be using the link you provided to assist in troubleshooting any issues, and will reply on this thread if I see a reoccurance.
Interestingly these systems are bound with both an intranet/Public IP and a private address IP, so it's very possible binding issues are causing problems.