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

Database connection not available ConnectionWaitTimeoutException



Thread dumps cause slowness and JVM crash.

Error Messages

2017-04-14 16:08:19,017 [j2ee14_ws,maxpri=10]] [ STANDARD] [ PegaRULES:06.02] ( internal.access.DatabaseImpl) ERROR - There was a problem with the database when getting a list: Database-General Problem encountered when getting connection for database pegarules 0 Connection not available, Timed out waiting for 180002
From: (B55EA34AA62120FD75844EC84C204F7BF)
Caused by SQL Problems.
Problem #1, SQLState null, Error code 0: Connection not available, Timed out waiting for 180002

Steps to Reproduce

Perform a load test with a high volume of requestors.

Root Cause

A defect or configuration issue in the operating environment
A very high volume of requestors causes an insufficient number of connections to be available in the connection pool.


Perform the following local-change to increase the number of connections in the WebSphere Application Server:
  1. Set the Maximum Connections value to be higher, based on the environment needs in the WebSphere Application Server Admin Console, Resources > JDBC > Data Source.
  2. Go to IBM Support and search on swg21573982 to find the release note titled Default maximum connections size is too small in IBM Business Process Manager (BPM) 7.5

Published May 5, 2017 - 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