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

Getting daily OutOfMemory error on AES server



AES 7.1 is running on PRPC 7.1.5 and frequently throws OutOfMemory Errors.

Error Messages


Java heap space

Steps to Reproduce

Not Applicable

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. Execution of "Cleanup AES Data" Agent results in creation of huge (4Gig) ArraryList Object causing OOM error.
"Cleanup AES Data" Agent processes/deletes entries from pegaam_exception table that has grown to a large size (e.g 100 Million rows). Hence, every time the Agent runs, it brings large amount of data to the Clipboard causing heap exhaustion.


This issue is resolved through the following local change: Remove/Delete entries from this table that are older than 14 days by running DELETE SQL -
delete from pegaam_exception where pxCreateDateTime < [fourteendaysago]

"Cleanup AES Data" Agent will now be able to process relatively this manageable amout of data and keep the table size within limits.

Published June 12, 2015 - Updated December 2, 2021

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