Monitor Server Managed Service Shows As A Failed State In The Weblogic GUI

(Doc ID 2052256.1)

Last updated on JULY 17, 2017

Applies to:

Management Pack for Oracle GoldenGate - Version and later
Information in this document applies to any platform.


After running successfully for 6-8 weeks, Monitor v12.1.3 server UI becomes
unavailable. WLS console is accessible and shows Monitor managed server in a
FAILED state.

The MONITORSERVER_server1 shows a thread deadlock:

####<Apr 28, 2015 11:24:44 PM EDT> <Critical> <WebLogicServer> <ga016vd027>
<MONITORSERVER_server1> <[ACTIVE] ExecuteThread: '5' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <>
<3fbc05f7-b176-41bb-b100-45bb14791752-0001a9ab> <1430277884531> <BEA-000394>
<Deadlock detected:
[deadlocked thread] DoubleQueuesAsyncGgsEventsDispatcherImpl_Thread-27:
Thread 'DoubleQueuesAsyncGgsEventsDispatcherImpl_Thread-27' is waiting to
acquire lock 'java.lang.Object@4397f096' that is held by thread '[ACTIVE]
ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)''

stack trace

####<Apr 28, 2015 11:25:51 PM EDT> <Error> <Health> <ga016vd027>
<MONITORSERVER_server1> <[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <>
<3fbc05f7-b176-41bb-b100-45bb14791752-0001a9b4> <1430277951138> <BEA-310001>
<Subsystem ServerRuntime has failed. Setting server state to FAILED.>


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