Legacy Knowledge Base
Published Jun. 30, 2025

ConnectionPoolTimeoutException: Timeout waiting for connection from pool when full reindex

Written By

Kanchan Bisht

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

  • As an Admin, users want to be able to decide if they want to cache extracted text when indexing so that if they are doing re-indexing they can disable this cache.
  • In 7.4, there is an HTTP request call to S3 and check if the file exists when the file is indexing. This block of code requests to S3 on every file re-index and causes a timeout issue when there are a lot of files re-indexing. The file extension validation is done after that to determine if the file content should be indexed. While in 7.3 the file extension is checked first to determine if the file content should be indexed.

Environment

  • Liferay DXP 2023.Q4.0

Resolution

  • The reported behavior is because of the change that was made in LPS-173162. 
  • This has been addressed via LPD.
     

Additional Information

  • Please submit a support ticket to request the hotfix that includes these LPS and see if it resolves the reported behavior.
  • Installing Fix Packs and Hotfixes on Liferay DXP will guide you to install the Fixpack or Hotfix in your environment.
Did this article resolve your issue ?

Legacy Knowledge Base