Question
3
Replies
704
Views
Vodafone
Posted: July 4, 2019
Last activity: October 24, 2019
Closed
Observed lot of PEGA0001 & PEGA0069 alerts in production
Hi,
we are observing many PEGA0001 & PEGA0069 in alert file. when we checked AES for browser performance, we could see PAL statistics as below.
For most of the alerts, pxRDBIElapsed is high which caused total elapsedtime to be high. End user response is critical because of this.
Please recommend how to fix this issue
Hello,
If your alert log contains a large number of PEGA0069 messages, a problem on the server, network, or client might be causing screens to take a long time to load. Using the message text, compare the load duration to the server duration to narrow down the issue to the server, client, or network. The action specified in the alert message can also help you determine which screen or action caused the alert.
Other alerts that are triggered by this screen load have the same requestor ID and page load counter as the PEGA0069 alert. You can use this information to correlate those alerts to the PEGA0069 alert.It will be dependent on some other alert. Try to find out a pattern It will help to get the root cause.
The following articles might help you to understand more about PEGA0069 & PEGA0001:
https://community.pega.com/knowledgebase/articles/pega0001-alert-http-interaction-time-exceeds-limit
https://community.pega.com/knowledgebase/pega0069-alert-client-page-load-time