Legacy Knowledge Base
Published Sep. 10, 2025

Implicit connection cache issue

Written By

Thanga Meena

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Looking into the thread dumps, few threads were getting stuck as below with OracleImplicitConnectionCache and running out of implicit connection cache issue
tomcat-http--300 - priority:5 - threadId:0x00007f6ac4286000 - nativeId:0x960 - nativeId (decimal):2400 - state:TIMED_WAITING
stackTrace:
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at oracle.jdbc.pool.OracleImplicitConnectionCache.processConnectionWaitTimeout(OracleImplicitConnectionCache.java:3050)
- locked <0x000000072f081790> (a oracle.jdbc.pool.OracleImplicitConnectionCache)
at oracle.jdbc.pool.OracleImplicitConnectionCache.getConnection(OracleImplicitConnectionCache.java:388)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:428)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:202)

Environment

  • Liferay portal 6.2EE
  • Oracle Database 12c

Resolution

Kindly note, the provided unofficial links are not the official documentation from Liferay, you can choose to use and follow these at your discretion by connecting with your DB or technical team.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base