Question2Replies684Views saikrishnaCSK Member since 2015 16 posts Instellars Posted: January 17, 2019Last activity: November 22, 2019 Closed Pega0028, Pega0017 Alerts are generated frequently in logsi feel that these alerts are generated because pega(jvm) failed to reclaim the memory and purge the long lived object. is it correct? if yes, can we do anything explicitly?Suggest the actions to take to prevent these alerts in logs.Thanks Pega Platform System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 1 year agoUpdated: 1 year agoMahesh Midthuru PEGA replied to saikrishnaCSKHi Sai, You need to go through the respective documentation for these 2 alerts to understand probable reasons behind this alert and the preventive actions for it as follows, https://community.pega.com/knowledgebase/articles/performance/pega0028-alert-gc-cannot-reclaim-memory-memory-pools https://community.pega.com/knowledgebase/articles/pega0017-alert-cache-exceeds-limit Go through this documentation and analyze with your application configurations to identify the root cause behind this failures then take the preventive actions as suggested in the alert docs. Hope that might help you going forward. Regards Mahesh M Posted: 1 year agoARVINDMALAV PEGA replied to saikrishnaCSKIn addition to Mahesh comments, I would suggest you review high value instance of these alerts in PDC/AES to see which part of application these are generating from?