BAM STUCK thread on oracle.beam.common.event.jms.SynchronousEventReceiver

(Doc ID 2272713.1)

Last updated on AUGUST 16, 2017

Applies to:

Oracle BAM (Business Activity Monitoring) - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

Bam Server experiences stuck threads

"[STUCK] ExecuteThread: '40' for queue: 'weblogic.kernel.Default
(self-tuning)'" #154 daemon prio=1 os_prio=0 tid=0x00007f886cc0b800
nid=0x6e88 in Object.wait() [0x00007f88d7efa000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at
oracle.beam.common.event.jms.SynchronousEventReceiver$ListenerThread.stopThread(SynchronousEventReceiver.java:817)
- locked <0x000000041fe1bdc8> (a java.lang.Object)
at
oracle.beam.common.event.jms.SynchronousEventReceiver.stopReceiver(SynchronousEventReceiver.java:414)
- locked <0x000000041fe117c8> (a
oracle.beam.common.event.jms.SynchronousEventReceiver)
at
oracle.beam.datacontrol.provider.activedata.AbstractChangeListListener.unRegisterAsMessageConsumer(AbstractChangeListListener.java:272)
- locked <0x000000041fe11790> (a
oracle.beam.datacontrol.provider.activedata.SimpleChangeListListener)



Cause

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