My Oracle Support Banner

Soa-infra Deployment is not Starting (Doc ID 1474641.1)

Last updated on APRIL 06, 2017

Applies to:

Oracle Fusion Application Toolkit - Version 11.1.2.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 1MAY2014***

Symptoms

The soa_server1 managed server is up and running, but the soa-infra deployment is down.

In the soa_server1.out the following error was occurring:

<Jul 7, 2012 8:57:00 PM CDT> <Error> <Coherence> <BEA-000000> <2012-07-07 20:57:00.621/552.800 Oracle Coherence GE 3.6.0.4 <Error> (thread=Cluster, member=n/a): Detected soft timeout) of {WrapperGuardable Guard{Daemon=IpMonitor} Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.6}}>
<Jul 7, 2012 8:57:26 PM CDT> <Error> <Coherence> <BEA-000000> <2012-07-07 20:57:26.124/578.303 Oracle Coherence GE 3.6.0.4 <Error> (thread=Cluster, member=n/a): Failure to join a cluster for 300 seconds; stopping cluster service.>
<Jul 7, 2012 8:57:26 PM CDT> <Error> <Coherence> <BEA-000000> <2012-07-07 20:57:26.159/578.338 Oracle Coherence GE 3.6.0.4 <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_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:637)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)


After enabled the Coherence logging the following errors were seen in the coherence.log:

2012-07-11 08:09:25.490/187.560 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2012-07-11 08:08:54.707, Address=IPAddress:Port1, MachineId=18883, Location=site:mydomain,machine:mymachine,process:28213, Role=WeblogicServer) has been attempting to join the cluster using WKA list [mymachine/IPAdress:Port2] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.
2012-07-11 08:09:25.490/187.560 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond

 

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
References


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