Implicit Connection Cache (ICC) Leaks Threads When Failure in Initialization
Last updated on AUGUST 03, 2016
Applies to:JDBC - Version: 10.2.0.1 to 18.104.22.168 - Release: 10.2 to 11.2
Information in this document applies to any platform.
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)
Timeouts are being used for the Implicit Connection Cache, for example:
AbandonedConnectionTimeout or InactivityTimeout.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms