Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

PEGA0017 alert: Cache exceeds limit

Suggest edit Updated on January 21, 2022

The PEGA0017 alert is triggered when a cache size exceeds the limit value and indicates that the instances of the stated cache are being invalidated (purged).

Like the PEGA0016 alert, this setting relates to various caches in the system. When entries stored in a cache exceed the limit value (not the target value) set in Data-Admin-System-Settings (DASS), the oldest entries in the cache are immediately invalidated until the count of entries in the cache is below the target limit. The alert message specifies which of the following caches was affected:

  • fua/global
  • fua/personal
  • PropertyReference
  • LowerCase
  • UpperCase

Example message text

collections/mru/UpperCase: Successfully reduced MRU by 3002 down to: 15000.

Default settings

fua/global/instancecountlimit - 20000

fua/personal/instancecountlimit - 20000

collections/mru/PropertyReference/instancecountlimit - 10000

collections/mru/LowerCase/instancecountlimit - 10000

collections/mru/UpperCase/instancecountlimit - 15000

Probable reasons for the alert and next steps

When this alert occurs, it is a strong indication that the cache limit setting is too low.

A cache that is too small hurts performance by requiring more objects to be fetched from the database (or fetched from the file system or loaded by a class loader) than from the cache.

Did you find this content helpful? YesNo

87% found this useful

Have a question? Get answers now.

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

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