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

PEGA ALerts log rapidly increasing and Exhausting Memory



In one of the Prod Node, The Pega Rules Alert file is increasing rapidly and causing the available memory Exhausted.

Error Messages

Disk space is full alert triggered for every hour.

From the PegaRULES-ALERT log:

2017-06-02 13:38:50,559 GMT*6*PEGA0040*141110308*3000000*f773caecb6b49217b2244a9dab977eee*A748BBA1F31E1373AE977EDCC73980934*none*<Class>*MyAgents:01.01.01*bc6e8aba19bd40d5ec9328c29195ca23*N*35*1395*ajp-apr-<IP Address>-11009-exec-17*STANDARD**<server>|<IP>|SOAP|<ServiceName>|Services|ReceiveDocument|A748BBA1F31E1373AE977EDCC73980934*ServicePAL.SOAP.<ServiceName>.Services.ReceiveDocument*Rule-Obj-Activity:
*Wrote blob to database with compressed size 141110308. pzInsKey: DATA-WORKATTACH-FILE ACME-FW-WILY-WORK RR-123456!20170602T133839.742 GMT*

Steps to Reproduce

Not applicable

Root Cause

An issue in the custom application code or rules: The massive alert logs are being caused by Pega0040 alerts that appear to include the content of the serialized stream that is processed. The alert (BLOB size written to the database exceeded a threshold) is due to the massive PDF file being used. The compressed size is 141MB​


Perform the following local-change: The usage of such large attachments should be avoided. To help avoid Pega0040 alerts for these massive attachments you can either disable the Pega0040 alerts or increase the threshold appropriately. Either of these will really be a temporary solution as the attachment size and how they are being handled needs to be revisited by your development team.

Suggest Edit

Published August 26, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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