My Oracle Support Banner

After New Install, WLS_Reports Will Not Start. (Doc ID 2643103.1)

Last updated on MARCH 04, 2020

Applies to:

Oracle Coherence - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

After a new install of FMW 12.2.1.3 (Forms and Reports), starting the WLS_Reports managed server returns coherence related error:

#### <WLS_REPORTS> <Logger@9267279 12.2.1.3.0> <> <> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > (thread=Transport:TransportService, member=n/a): validatePolls: This service timed-out due to unanswered handshake request. Manual intervention is required to stop the members that have not responded to this Poll
..
..
#### <WLS_REPORTS> <Logger@9267279 12.2.1.3.0> <> <> <[severity-value: 256] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <[com.tangosol.coherence.component.util.logOutput.Jdk:log] 2020-02-20 10:27:00.876/320.158 Oracle Coherence GE 12.2.1.3.0 (thread=Transport:TransportService, member=n/a): Service TransportService left the cluster>
#### <WLS_REPORTS> <Logger@9267279 12.2.1.3.0> <> <> <[severity-value: 256] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <[com.tangosol.coherence.component.util.logOutput.Jdk:log] 2020-02-20 10:27:01.240/320.522 Oracle Coherence GE 12.2.1.3.0 (thread=Cluster, member=n/a): Service Cluster left the cluster>
#### <WLS_REPORTS> <Logger@9267279 12.2.1.3.0> <> <> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > (thread=[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=1, Name=TransportService, Type=Transport
..
..
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.startSystemServices(Cluster.CDB:11)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:53)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:12)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:32)
at com.tangosol.coherence.component.util.SafeCluster.getRunningCluster(SafeCluster.CDB:7)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:5)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:580)
at weblogic.coherence.service.internal.WLSCoherenceConfigurator$EnsureClusterStartingTask.run(WLSCoherenceConfigurator.java:219)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:670)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)
..
..
#### <WLS_REPORTS> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
The full error can be viewed in the attached WLS_REPORTS_krishnaweb.log around the the Feb 20, 2020 10:27 timestamp.

The attached log includes setting admin console -> Reports managed server > logging tab -> for "Platform logger levels" , add com.oracle.coherence.level=FINEST

Possible related note - Error While Starting Cluster: Com.tangosol.net.RequestTimeoutException: Timeout During Service Start (Doc ID 2584446.1)

Tried adding the -Dcoherence.localhost= to Admin Server, WLS_Reports and WLS_Forms server start, but same behavior occurred.

Changes

 

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
Changes
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.