After Upgrading to OC4J 10.1.2.2, JDBC Pooled Connections are Created and Closed Continuously
(Doc ID 781570.1)
Last updated on FEBRUARY 13, 2024
Applies to:
Oracle Containers for J2EE - Version 10.1.2.2.0 to 10.1.2.2.0 [Release AS10gR2]Information in this document applies to any platform.
OC4J 10.1.2.2
Not reproducible on OC4J 10.1.2.0.2
Fixed on OC4J 10.1.2.3
Symptoms
After upgrading from 10.1.2.0.0 / 10.1.2.1.0 to 10.1.2.2.0 Oracle Application Server, OC4J creates and closes JDBC connections without using the connection pooling.
An application is retrieving JDBC connection from an Emulated Datasource which is configured with min-connections and inactivity-timeout connection pool parameters.
The issue is that retrieved JDBC connections from the pool are immediately closed by OC4J instead of being pooled after their use. The inactivity timeout parameter has no effect.
As a consequence, the overall system performance goes down dramatically. This issue can impact OC4J performance and OC4J has to be restarted from time-to-time due to lack of response.
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 |
| References |