My Oracle Support Banner

OAM 11.1.2.3.0 While Starting OAM Managed Server Receive Error 'Failed To Start Service "Cluster"' (Doc ID 2369872.1)

Last updated on MARCH 07, 2018

Applies to:

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

Symptoms

When attempting to start an OAM managed server, the following errors appear:

<Feb 9, 2018 10:09:27 PM GMT> <Error> <Coherence> <BEA-000000> <2018-02-09 22:09:27.542/175.136 Oracle Coherence GE 3.7.1.13 <Error> (thread=Cluster, member=n/a): Member(Id=1, Timestamp=2018-02-09 22:09:24.164, Address=192.168.1.1:9095, MachineId=30872, Location=site:,machine:oammachine,process:9920, Role=WeblogicServer, Edition=Grid Edition, Mode=Production, CpuCount=176, SocketCount=176) UID=0xzzzzzzz000001617C9DAEC478982387 is unable to join the cluster.>
<Feb 9, 2018 10:09:27 PM GMT> <Error> <Coherence> <BEA-000000> <2018-02-09 22:09:27.542/175.136 Oracle Coherence GE 3.7.1.13 <Error> (thread=Cluster, member=n/a): This member is not authorized to join the cluster.>
<Feb 9, 2018 10:09:27 PM GMT> <Error> <Coherence> <BEA-000000> <2018-02-09 22:09:27.554/175.148 Oracle Coherence GE 3.7.1.13 <Error> (thread=[ACTIVE] ExecuteThread: '1' 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_ANNOUNCE)
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)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:56)

Cause

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
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.