My Oracle Support Banner

ORA-00060 Deadlock Detected when Using SOA AQ JMS (Doc ID 1333179.1)

Last updated on APRIL 23, 2019

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


When using AQ JMS deadlock is detected on the database and is accompanied by the following error in the database trace file:

[Transaction Deadlock]
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TM-0000d58a-00000000 141 1772 SX 141 1772 X
session 1772: DID 0001-008D-0014D368 session 1772: DID 0001-008D-0014D368
Rows waited on:
Session 1772: no row
Information on the OTHER waiting sessions:
End of information on OTHER waiting sessions.
Current SQL statement for this session:
begin dbms_aqadm_sys.add_subscriber(queue_name => :1, subscriber => :2, rule => :3, security_check => true, add_jms_entry => true, transformation => :4, properties => :5); end;
----- PL/SQL Call Stack -----
object line object
handle number name
70000006e8a0d90 615 package body SYS.DBMS_AQADM_SYSCALLS
70000006e5023a8 5358 package body SYS.DBMS_AQADM_SYS
70000006e3edeb8 1 anonymous block
70000006e507048 129 package body SYS.DBMS_AQJMS
70000005c3ae7f8 1 anonymous block


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.