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.

Troubleshooting: "Connection Pool Manager could not allocate a Managed Connection" error (WebSphere)

Suggest edit Updated on May 7, 2019

Symptom

When using WebSphere, the default number of database connections for each Java Virtual Machine (JVM) is 10. For example, if you have two JVMs supporting an application, then you have 20 database connections by default.

Often for Process Commander applications, 10 database connections are not sufficient. If you have an insufficient number of database connections, users will experience performance issues, and the following error may appear in the PegaRULES log file:

[4/10/07 14:57:49:360 EDT] c1e279e ConnectionMan E J2CA0020E: The Connection Pool Manager could not allocate a Managed Connection: com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 180007

 

Solution

Explanation

This error occurs when the connection pool reaches its maximum size, all connections are in use, and the connection timeout parameter expires.

 

Resolution

Use the WebSphere Administration console to set the number of database connections to 25 for each JVM.

If 25 database connections is still insufficient, increase the number by ten until you reach the number of connections your system needs to run efficiently.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us