JDBC Connection Leak When Transaction Is Timed Out In Oracle Application Server 10.1.3.4
(Doc ID 1066004.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.4.0 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 28-Mar-2014***
A J2EE application is deployed into 10.1.3.4 OC4J.
This application retrieves a JDBC connection from an OC4J configured datasource to participate in a global transaction.
The problem is a JDBC connection leak which occurs with the following sequence :
- Due to a transaction timeout, the global transaction is rolled back.
- And, accessing to the JDBC connection (retrieved from configured datasource ), an exception (java.sql.SQLException: javax.resource.ResourceException: RollbackException) is thrown.
The problem is that the allocated JDBC connection is not put back to the connection pool (related to the datasource). As a consequence, a JDBC connection leak is observed.
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