Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Connection pool Exhausted on reindexing search



Customer migrated the rules and data to stage environment and search is not working for newly migrated work objects. While trying to reindex rule, data and work objects, the connection pool issue is reported. 

Error Messages

Caused by SQL Problems.
Problem #1, SQLState null, Error code 0: weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool jdbc/PegaRULES is Suspended, cannot allocate resources to applications..
Problem #2, SQLState null, Error code 0: java.sql.SQLException: Cannot obtain connection: driverURL = jdbc:weblogic:pool:jdbc/PegaRULES, props = {EmulateTwoPhaseCommit=false, connectionPoolID=jdbc/PegaRULES, jdbcTxDataSource=true, LoggingLastResource=false, dataSourceName=jdbc/PegaRULES}

Steps to Reproduce

Just type and existing rule/data/work object instance name in the search bar and hit search.

Root Cause

A defect or configuration issue in the operating environment


Here’s the explanation for the reported behavior:

The process to upgrade to ES must be completed manually, as follows:
  • From the Search Landing Page, verify that there is a single valid host node ID and directory location defined, where the ES index files will initially reside.
  • Verify that there is enough space in this directory location for the ES index files. Allocate 3 times the amount of space used by the Lucene index files. This extra space is recommended to allow ES to perform automatic index management in which it merges data in various segments of the index to optimize performance.  If the node also hosts the Lucene index files, this amount of space is needed in addition to that required for the Lucene index files, since they remain on the node following the build of the ES index files;  they may be erased following successful completion of the ES index file builds.
  • Open a port on each node of a multimode cluster for ES node-to-node communications, as described in the Developer Help topic for the search landing page on the PDN.
  • Alert messages for index builds and re-builds should be enabled by the customer on the search landing page, so that an alert message will be sent anytime there is an error during an index rebuild.
  • Manually build (using the Re-Index button) the desired index files for Work-, Data-, and/or Rule-. When any of these index files are built, a check is performed internally to verify that all requested ES index files have been built, and if true, subsequent searches automatically switch over from Lucene to ES.
    ·         Two dynamic system settings control the use of ES rather than Lucene following an upgrade:  indexing/distributed/index_enabled and indexing/distributed/search_enabled.
    ·         Both settings are true for a new install. For upgrades, indexing/distributed/index_enabled is true and indexing/distributed/search_enabled is false, but set true after the ES index files are built
Customer mentioned and search is working fine but connection pool is less and re -index is failing so  requested customer to increase the connection pool and try to re-index. Customer yet to do it.

Published March 4, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us