OC4J Managed Datasource Not Reusing Or Leaking Connections In Pool
(Doc ID 396059.1)
Last updated on JULY 03, 2020
Applies to:Oracle Containers for J2EE - Version 10.1.3.0.0 and later
Information in this document applies to any platform.
Custom application uses OC4J 10.1.3 managed connection pooling.
The goal is for connection pooling to maintain specified minimum connections and to reuse the connections in connection pool. When the application is run, this will avoid the number of used connections to keep increasing until maximum number of sessions on database is reached, ultimately causing the database to crash.
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