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

Large number of PEGA0026 alerts in the log file



Performance is poor after migrating to Pega 7.1.7. large number of PEGA0026 alerts are observed in the log file.

Error Messages

Time to acquire a connection has exceeded the alert threshold of 100 ms

Steps to Reproduce

There is no specific use case to reproduce this issue.

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment.

There are two issues:
  • Large number of PEGA0026 alerts. Refer the PDN article to know more -
  • A Guardrail query was timing out. This is because the query was too complex and would take too long to finish. The timeout was introduced in Pega 7.1.7 to prevent query running for too long.


  • Set InitialSize of Connection pool to be same as Max size to avoid time spent in resizing the pool.
  • Remove the part of the section calling the guardrail report, if needed.

Published July 31, 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