PEGA0043 alert: Queue waiting time is more than x for x times

The PEGA0043 alert is generated when asynchronous load of declare pages is enabled and the requestor wait time exceeds the threshold more than the specified number of times. Each time these conditions are met, an additional alert is raised. For example, if the threshold for wait time in the queue is 2 seconds, and the number of times the wait time must exceed the threshold is 25, then the following actions occur:

  • An alert is generated each time an asynchronous data page (ADP) waited in the queue for 2 seconds more than 25 times.
  • A second alert is generated when these conditions are met again, for example, when an ADP waited in the queue for 2 seconds more than 50 times.

Example message text

​Queue waiting time is more than 2 sec for 1325 times.

Default prconfig.xml settings

Two settings in the prconfig.xml file affect this alert:

  • <env name="alerts/ADP/queuewait/thresholdtime value="2" />
    Indicates the wait time in the queue, in this case, 2 seconds.

  • <env name="alerts/ADP/queuewait/thresholdcount value="25" />
    Indicates the number of times that the wait time (ADP/queuewait/thresholdtime) can be exceeded before an alert is generated, in this case, 25 times.

For information about editing values in the prconfig.xml file, see How to set prconfig values in a Dynamic System Setting value. For information about adjusting the alert threshold for a single node in a multinode system, see How to change prconfig.xml file settings.

Reason for the alert

There were more requests than requestors. You can increase the Maximum Active Requestors on the AsyncDeclarativePool Service Package Pooling tab to decrease the wait time.

Additional information

How to configure non-blocking UI using Asynchronous Declare Pages

Performance alerts, security alerts, and AES

Alert log message data

Have a question? Get answers now.

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