Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Troubleshooting: "ConnectionWaitTimeoutException" with JDBC datasource (WebSphere)

Updated on May 7, 2019


The WebSphere application server becomes unresponsive and the following error appears in the log file:

27/06/06 10:25:41:506 GMT]  111e86f SystemOut   O 10:25:41,503 [sage Tracking
 Daemon] (      engine.database.Opener) ERROR  - There was a problem opening a
Database-General      Problem encountered when getting connection for database
 PegaRULES    0         Connection not available, Timed out waiting for
(BD914C390476DA38C9B1CDBBD02C5BB7D:(Usage Daemon)) Database-General   Problem
encountered when getting connection for database PegaRULES    0
Connection not available, Timed out waiting for 180006
      at com.pega.pegarules.engine.database.ExceptionInformation.createExcepti
      at com.pega.pegarules.engine.database.ConnectionManager.getConnection(Co
      at com.pega.pegarules.engine.database.ConnectionManager.getConnection(Co
      at com.pega.pegarules.engine.database.ThreadConnectionStore.getConnectio
     . . . 24 more . . .
Caused by: Connection no
t available, Timed out waiting for 180006
      at com.pega.pegarules.engine.database.DataSourceManager.getConnection(Da
      at com.pega.pegarules.engine.database.DatabaseConnection.activate(Databa
      at com.pega.pegarules.engine.database.ConnectionManager.getConnection(Co
      ... 22 more
Caused by SQL Problems.
Problem #1, SQLState null, Error code 0: Connection not available
, Timed out waiting for 180006
     . . . 26 more . . .


This issue only applies to a Process Commander system which has been configured to use a WebSphere JDBC Data Source.

When the maximum number of connections in the WebSphere connection pool has been reached, no new connections are created. If Process Commander attempts to service a request at this time, the requestor has to wait until a connection becomes free, i.e. a connection is returned to the pool. The WebSphere connection pool manager throws a ConnectionWaitTimeoutException if the request for a connection times out before a free connection becomes available.




Using the WebSphere Administrative Console, review your connection pool settings:

WebSphere 5.x


WebSphere 6.x


Check the value of the MaxConnections property. By default, this property is set to 10. In a Process Commander system with a large number of concurrent users, the default setting for the MaxConnections property may be too low. Try increasing the MaxConnections property to a higher value.

If the problem persists after tuning the WebSphere connection pool, it is possible that you are experiencing a connection leak. For information on the WebSphere connection leak trace feature, see the IBM Tech Note at WWW

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us