Troubleshooting a Coherence Node That Cannot Join a Service
Last updated on APRIL 15, 2018
Applies to:Oracle Coherence - Version 18.104.22.168 and later
Information in this document applies to any platform.
***Checked for relevance on 22-FEB-2013***
***Checked for relevance 15-AUG-2014***
When a Coherence node joins a cluster, it must receive confirmation from every node in the cluster for every service that it is configured to run. If a new node does not receive confirmation for a service, it will not be able to join it. Therefore, the goal is to identify the node(s) with the unresponsive service thread and remove it from the cluster by shutting down its JVM.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms