Legacy Knowledge Base
Published Sep. 10, 2025

There are more database connections than allowed by jdbc.default.maxPoolSize

Written By

Ricardo Couso

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

  • The maximum pool size of connections to the database is explicitly limited via the property jdbc.default.maxPoolSize.
  • Nevertheless, the number of connections exceeds this maximum pool size.

Environment

  • Liferay DXP 7.0+

Resolution

  • This can the expected behavior.
  • The extra number of connections can be accounted for by a second connection pool related to Counters.
  • By default this second pool makes use of the same parameters as the principal one.
    • This can be changed by modifying the appropriate prefix, using the property counter.jdbc.prefix.
    • This property has the default value jdbc.default..

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base