Table of Contents

Identify performance issues with queue processor and job scheduler activities (8.5)

Improve the performance of your application’s activities, which often access databases or external services, by analyzing new alert messages. When a queue processor activity or a scheduled job runs longer than the threshold value, Pega Platform™ now saves an alert in the performance alert log. You can analyze these alerts directly in the log or by using Pega Predictive Diagnostic Cloud™ (PDC) to identify and address potential performance issues with long-running processes.

For example, for a Queue Processor rule for sending emails to users, the Long running queue processor threshold for the rule is 5000 milliseconds, or 5 seconds. When the rule runs as scheduled, email processing takes 25 seconds, which exceeds the threshold. Pega Platform saves the PEGA0117 alert: Long-running queue processor activity to the log file. Upon investigation, you discover that the cause for the excessive processing time is an issue with network latency and the email server’s responsiveness. Therefore, you restart the email server. The next time the send email queue process runs, the activity ends after 4.5 seconds, which is within the threshold, and no alert is generated.

The following figure shows the threshold configuration for the Queue Processor rule: 

The Long running queue processor threshold for a dedicated queue process
The Long running queue processor threshold for a dedicated queue process


For more information about the possible reasons for the alerts, examples of the alerts, and steps involved in resolving issues, see:

Did you find this content helpful?

100% found this useful

Have a question? Get answers now.

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