Implicit Connection Cache (ICC) Leaks Threads When Failure in Initialization
(Doc ID 1369218.1)
Last updated on AUGUST 30, 2023
Applies to:
JDBC - Version 10.2.0.1 to 11.2.0.3.0 [Release 10.2 to 11.2]Information in this document applies to any platform.
Symptoms
Implicit Connection Caching (ICC) is being used.
If for some reason the Implicit Connection Cache cannot be initialized and timeouts are being used in the ICC configuration, then for every initialization attempt there will be a Thread leak with the following stack:
"Thread-2498" daemon prio=10 tid=0x000000005f892800 nid=0x213e waiting on condition [0x00002aab7356d000] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at oracle.jdbc.pool.OracleImplicitConnectionCacheThread.run(OracleImplicitConnectionCacheThread.java:91)
Changes
Implicit Connection Cache is being used and cannot be initialized.
Timeouts are being used for the Implicit Connection Cache, for example:
AbandonedConnectionTimeout or InactivityTimeout.
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 |