New Node of cluster  startup Error: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)

(Doc ID 2101858.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


You have extended new oam_server in the cluster. After that, we are not able to start up the new OAM Server.

Below Coherence errors are seen:

GCoherence error while trying to start the third server in a cluster:

<Jan 12, 2016 2:05:05 PM GMT> <Error> <Coherence> <BEA-000000> <2016-01-12 14:05:05.433/356.673 Oracle Coherence GE <Error> (thread=Cluster, member=n/a): This member is not authorized to join the cluster. Rejected by Member(Id=3, Timestamp=2016-01-10 09:58:09.953, Address=, MachineId=25621, Location=site:,machine:GBVLS-AS182,process:32757, Role=WeblogicServer).>
<Jan 12, 2016 2:05:05 PM GMT> <Error> <Coherence> <BEA-000000> <2016-01-12 14:05:05.439/356.679 Oracle Coherence GE <Error> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:38)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)



 You added a new OAM Server to the cluster.


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