My Oracle Support Banner

Deadlock / client hang When Using Aq Through Jms (Doc ID 313515.1)

Last updated on JANUARY 17, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.6 and later
Information in this document applies to any platform.
Archived on 24-Aug-10


Symptoms

AQ jms message notification

Occassionally , there is a deadlock between threads which publish message to a jms
topic and thread which receives message through callback (OnMessage method).
Sender as well as receiver may commit simultanously.

There are also occassional ora-4020 errors generated in trace files on the server.
These errors are self deadlock errors against the queue table itself.

When the hang is encountered, a systemstate dump shows that there are no processes on the server
side which are blocking each other.

i.e issuing will give more details regarding :
oradebug setmypid
oradebug unlimit
oradebug dump systemstate 10
wait 2 minutes :
oradebug dump systemstate 10

the trace file produced in the user_dump_dest location will have more details regarding the hang.

In other words the issue appears to be client or jdbc related .

Verified that issue is jdbc driver/client side related by examining systemstates for interprocess dependencies
No dependencies were observed

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution

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