Troubleshooting a Coherence Node That Cannot Join a Service (Doc ID 845363.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Coherence - Version 2.5.1 to 12.1.3.0.0
Information in this document applies to any platform.
***Checked for relevance on 22-FEB-2013***
***Checked for relevance 15-AUG-2014***

Goal

This guide assumes that the node can join the cluster, but can't join a service.  If the node cannot join a cluster, ensure that multicast is functioning correctly via the Multicast test or that WKA (Well Known Addresses) is correctly configured.


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.

Solution

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