My Oracle Support Banner

BPEL AQ adapter stops reading from AQ (Doc ID 371005.1)

Last updated on DECEMBER 19, 2019

Applies to:

Oracle(R) BPEL Process Manager 10g - Version to
Generic (Platform Independent)
Checked for relevance on 23-Apr-2010
***Checked for relevance on 20-Mar-2012***


AQ adapter stops dequeuing messages. To diagnose the problem use the following steps:

1. run command

opmnctl status -l

it will show process ID of the OC4J_BPEL instance.

2. execute the following command

kill -3 <process_id from step 1>

As a result of this command a stack trace will be written to the OraBPEL~OC4J_BPEL~default_island~1 log file.

This is a typical stack trace that you might get:

1  LKDEADLOCK Deadlock detected !!!
NULL ---------------------

2  LKDEADLOCKTHR Thread "JCA-work-instance:AQ Adapter-5" (0x3FD30DA0)

3  LKDEADLOCKWTR is waiting for:
4  LKDEADLOCKMON sys_mon_t:0x40F50128 infl_mon_t: 0x40F3FC18:
4  LKDEADLOCKOBJ oracle.jdbc.driver.T4CConnection@50EB1138/50EB1140:
3  LKDEADLOCKOWN which is owned by:
2  LKDEADLOCKTHR Thread "ApplicationServerThread-25" (0x3BF8E6A0)

3  LKDEADLOCKWTR which is waiting for:
4  LKDEADLOCKMON sys_mon_t:0x40F501D8 infl_mon_t: 0x00000000:
4  LKDEADLOCKOBJ oracle.jdbc.driver.T4CCallableStatement@51230A20/51230A28:
3  LKDEADLOCKOWN which is owned by:
2  LKDEADLOCKTHR Thread "JCA-work-instance:AQ Adapter-5" (0x3FD30DA0)


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

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