My Oracle Support Banner

Hundreds Of BAM BatchProcessorThreads Are Created And Stay On State WAITING (parking) (Doc ID 1553406.1)

Last updated on OCTOBER 17, 2017

Applies to:

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


On : BAM version and later,

Hundreds of BAM BatchProcessorThread are created and stay on state WAITING (parking) like this:

"BatchProcessorThread(685)" prio=3 tid=0x000000001247e800 nid=0x191638 waiting on condition [0xfffffd7ee6edf000]
  java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0xfffffd7fa80f4cf0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(
at java.util.concurrent.DelayQueue.take(
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(
at java.util.concurrent.ThreadPoolExecutor.getTask(
at java.util.concurrent.ThreadPoolExecutor$

The issue can be reproduced at will with the following steps:
1. Start Weblogic
2. Leave the system running
3. Take a thread dump and check the BatchProcessorThread, you will see the threads on state WAITING (parking) increase


To view full details, 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 a vibrant support community of peers and Oracle experts.