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

PEGA001, PEGA004, PEGA0039 and PEGA0042 alerts from OOTB rules



There are number of below mentioned Pega alerts in the Alert log files that occur on certain out-of-the-box (OOTB) activities and agents such as, CheckBulkProcessQueue, pzhandleassignmentmetadata, pxcasebreadcrumbpopulate, pzgetchildkeys and iteratrovereachimg. This impacts the application performance.

Alerts: PEGA0026, PEGA0001, PEGA0004, PEGA0039 and PEGA0042

Error Messages

Not Applicable

Steps to Reproduce

There is no specific use case to reproduce this issue.

Root Cause

A defect or configuration issue in the operating environment. The maximum connection pool on Websphere was set to 50 whereas the maximum number of users expected is 70. 
It is recommended to set the max connections to a number that is higher than the number of users expected to use the application as background processes may also require DB connections. Increasing the minimum connections also improves the performance, especially during application startup.


Perform the following changes on Websphere connection settings: 

Assuming that the number of users are 70, change the connection settings on Websphere as follows:

max connections = 100 
min connections = 50 

Published October 6, 2015 - 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