Hard for me to tell what's going on, without either being able to
reproduce this, or having access to logs. The former being much better
than the latter.
Your props look a bit weird, I would correct the following (and I
suggest using XML configs rather than string-based ones):
* UDP.loopback should be true, or else members don't get their own
suspicion messages. This might be the root problem...
* UDP.thread_naming_pattern cannot be "jgroups", but must be either
"C", "L", or "CL"
* GMS.view_ack_collection_timeout=10000: unusually high timeout
* GMS.join_timeout=11000: why such a high value ?
If you could reproduce this, and let me know how to do it (even if it
takes hours) that would be useful !
> Hi, we are starting testing JGroups 2.8GA and got the following, the
> system is stable for hours and suddenly the coordinator is rejected
> from the cluster by the other nodes and could not join back normally.
> We have been able to reproduce it several times with always the same
> behavior; nodes are not able to join back the cluster if excluded.
> Note: This is running under VMware, we look at the system and it
> stable low CPU and low Memory usage. Using JGroups 2.4 (with different
> JGroups properties) the system is stable for weeks.
> JGroups Version: 2.8GA
> We are setting all JVMs with :
> JGroups Properties:
Lead JGroups / Clustering Team