Coherence New Member/Node Cannot Join the Cluster Due To ManagedService Failure In Some Other Running Node/Member Of The Cluster
(Doc ID 2348027.1)
Last updated on MAY 06, 2022
Applies to:Oracle Coherence - Version 220.127.116.11.5 to 18.104.22.168.0 [Release 12c]
Oracle WebLogic Server - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 12c]
Information in this document applies to any platform.
Customer reported an issue about Coherence node member could not join coherence cluster. When customer tried to start a jmx node in the cluster, found the member is failing com.tangosol.net.RequestTimeoutException on startup. Customer did check the RemainingMemberSet in the senior node of the cluster and JMX node and then shutdown all nodes listed in the RemainingMemberSet list, but even then jmx node can't join the cluster, so customer finally shutdown node one by one and then tried whether it can restart again. However, until a particular member/node was restarted jmx member did not join the cluster. The member/node that was halted the jmx node start was a node it's Management service start was failed as its thread dump did not have the Invocation:Management & Invocation:Management:EventDispatcher threads.
Below is new node (jmx) error log entry:
We can't find Invocation:Management & Invocation:Management:EventDispatcher threads in Below is blocking node's/issue node's/failed node’s thread dump.
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