Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

3
Replies
1460
Views
 Ponnurangam Nagaraj (PonnurangamN2827) Vodafone
Vodafone
IN
PonnurangamN2827 Member since 2019 43 posts
Vodafone
Posted: July 4, 2019
Last activity: October 24, 2019
Posted: 4 Jul 2019 5:26 EDT
Last activity: 24 Oct 2019 8:06 EDT
Closed

Observed lot of PEGA0001 & PEGA0069 alerts in production

Report

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

System Administration
Posted: 3 years ago
Posted: 4 Jul 2019 5:56 EDT
Shiva Rakshith S (Rakshith) Technical Solutions Engineer
Pegasystems Inc.
IN
Report

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.

Show More

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


Show Less
Posted: 3 years ago
Posted: 4 Jul 2019 13:51 EDT
Abhinav Gupta (Abhinav7) PEGA Manager, Technical Support - Platform Service Engineering
Pegasystems Inc.
IN
Report

Hi,

Pega0001 comes if html page takes more than threshold time to load.It will come along with some other alerts.Please verify if you are getting any pega0005 or pega0020 alert.

Try to find out the pattern and resolve the root alert.It will remove pega0001 and pega0069 alert as well.

Thanks,
Abhinav
Posted: 3 years ago
Posted: 24 Oct 2019 8:06 EDT
Rimjhim Srivastava (srivr1) Pegasystems Inc. Senior Technical Solutions Engineer
Pegasystems Inc.
IN
Report

Pega0069 alerts if shown as top offender, indicates, there are performance issues.

Thus, you should review your Pega logs, Pega alert to see if there is an odd event, thread dump etc.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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