Skip to main content

Support Article

PEGA0017 alert: Cache exceeds limit



PEGA0017 and PEGA0037 alerts are generated in the logs.

Error Messages

PEGA0017 alert: Cache exceeds limit
PEGA0037 alert: Rule assembly time exceeded threshold

Steps to Reproduce


Root Cause

On verifying the JVM settings, the current values are low when compared to the proposed value.

-Xms3584m -Xmx3584m -XX:PermSize=384m -XX:MaxPermSize=512m

The proposed values are (according to the installation guide):

-Xms4096m -Xmx8192m -XX:PermSize=512m -XX:MaxPermSize=1024m

A change request is performed to change the infrastructure and to apply the correct JVM settings.

Additionally, Pega 7.1.7 introduced a new configuration, PruneToSoftPolicy. This configuration caches a soft reference to an element on pruning or draining. By default, this configuration is enabled. The softly referenced elements are not counted, like the mainstream cached elements, to determine the size of the cache as garbage collection may occur any time.
When PruneToSoftPolicy is disabled, the element is completely eliminated from the cache on pruning. Caching references with subscripts is stopped when the cache size reaches the set limit.


Perform the following local-change:
  1. Set the PruneToSoftPolicy option to False
  2. Increase the cache size for prconfig/collections/mru/PropertyReference/instancecountlimit to 350k.

Suggest Edit

Published March 30, 2018 - Updated October 8, 2020

Did you find this content helpful?

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 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