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 timeout errors during load test

SA-22787

Summary



When the user is performing a large load test, connection timeout errors are found in the PegaRULES log file.

Error Messages


2016-04-12 21:30:33,187 [PegaWorkManager : 12] [ STANDARD] [ ] [ ] ( internal.access.DatabaseImpl) ERROR - There was a problem with the database when getting a list:
com.pega.pegarules.pub.database.ConnectionException: Database-General Problem encountered when getting connection for database pegarules 0 CWTE_NORMAL_J2CA1009
From: (BCC2F66EFC83E60FA35BBCBE0775C64D0)
Caused by SQL Problems.
Problem #1, SQLState null, Error code 0: com.x.websphere.ce.cm.ConnectionWaitTimeoutException: CWTE_NORMAL_J2CA1009
...
Caused by:
com.x.websphere.ce.cm.ConnectionWaitTimeoutException: CWTE_NORMAL_J2CA1009
at com.x.ws.rsadapter.AdapterUtil.toSQLException(AdapterUtil.java:1680)
at com.xws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:661)
at com.x.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:611)
at com.pega.pegarules.data.internal.access.DataSourceManager.getConnection(DataSourceManager.java:221)
at com.pega.pegarules.data.internal.access.DatabaseConnectionImpl.activate(DatabaseConnectionImpl.java:1436)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnectionFromDataSourceIdentity(ConnectionManagerImpl.java:1008)
... 58 more
Caused by:
com.x.websphere.ce.j2c.ConnectionWaitTimeoutException: CWTE_NORMAL_J2CA1009
at com.x.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java:1783)
at com.x.ejs.j2c.PoolManager.reserve(PoolManager.java:3874)
at com.x.ejs.j2c.PoolManager.reserve(PoolManager.java:3094)
at com.x.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:1548)
at com.x.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:1031)
at com.x.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:644)
... 62 more


Steps to Reproduce



Run a high-volume load test.

Root Cause



A defect or configuration issue in the operating environment.

Resolution



Perform the following local-change: 

Increase the max database connections to 250 and test again.  A load test with 750 virtual users requires more than 50 connections. If 250 is not enough, you may need to increase again. Also, it is recommended to validate the connections as explained in the below PDN article and vendor documentation:

https://pdn.pega.com/support-articles/intermittently-dropping-db-connections-odn

 

Suggest Edit

Published June 30, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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