My Oracle Support Banner

Premature Transaction Timeout In Message-Driven Bean (Doc ID 1325806.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Containers for J2EE - Version 10.1.3.5.0 and later
Information in this document applies to any platform.

Symptoms

MDB bound to an Oracle AQ queue using the JMS API is deployed to SOA 10.1.3.5 MLR2 with the "Transaction timeout" set to 180 seconds in "orion-ejb-jar.xml".
In some cases a transaction timeout occurs although the runtime of the MDB's onMessage() method is far less than the transaction timeout of 180 seconds.

For example:

MDB is entered at 00:00:05293.
At 00:00:05298 (5ms later) Toplink tries to register with the transaction and gets a RollbackException which says
that the transaction is timed out already.

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
Cause
Solution
References


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