Question
Wells Fargo
IN
Last activity: 20 Jun 2017 14:38 EDT
PEGA0039 Alerts
we are seeing lot of PEGA0039 alerts while opening the workobjects and attachments. Read blob from database with compressed size 7070997 expanded size 14316076. how can we solve these kind of alerts? will this impact the Memory on the server? we have around 40 nodes and daily 4 nodes goes down.
***Moderator Edit: Vidyaranjan | Updated Categories***
BUPA
AU
Hi Shashi,
As per Pega's recommendation, all alerts are to be monitored and rectified to achieve optimal performance. Pls try to avoid the reading of Blob if possible.
The impact is at the memory level for the jvm. If you have any other memory intensive processes, they may compete.
Pls use the below link to have clear understanding.
https://docs-previous.pega.com/pega0039-alert-blob-size-read-database-exceeded-threshold
Updated: 20 Jun 2017 14:37 EDT
Wells Fargo
IN
I have analyzed all the relates to PEGA0039. The alerts are generating while opening work object which has attachments. Most of the alerts are from Pega OOTB Features. but I understand the root cause for all the alerts generating work objects have attachments.
can we fix that? I think its as per pega design to open attachments when work object is opened.
any thoughts?
Pegasystems Inc.
US
I would recommend finding the reason behind the system 'going down'. Was it due to OutOfMemoryError or something else? If it is OOM, try to capture a heap dump and analyze it using any memory analyzer tool to see if it is related to reading blob.