Coherence 220.127.116.11 - Client Node Hangs While Departing From Coherence Cluster
(Doc ID 1450995.1)
Last updated on JANUARY 31, 2019
Applies to:Oracle Coherence - Version 18.104.22.168 and later
Information in this document applies to any platform.
*** Checked for relevance 13-Oct-2014 ***
A client node which is exiting the cluster takes a thread dump, hangs, and goes into a bad (hung) state. This bad node prevents any other nodes from joining the cluster.
Based on the logs, you can see that the timeout on deregistering the management service is causing it to go into a bad state.
Below are the details from the logs . First the service guardian detects the thread has been unresponsive for its soft-timeout period, due to the dead-lock, and attempts to interrupt the thread:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document