LinkedIn
Copied!

Pega0046 alert: Queue entry not yet started upon by load activity

The PEGA0046 alert identifies issues in asynchronous data page processing. The alert is triggered when a findPage request is made, but the system cancels the background thread because it did not (or could not) start the loader activity in time to process the request. To avoid the processing incurred by starting the load activity in the background thread, the system processes the findPage request in the user thread. The alert identifies the data page involved.

Example message text

Queue entry not yet started upon by load activity (or a small chance it failed), Proceeding to load in user thread. DP [page name]& whose insKey is [pzInsKey]

The log displays the data page and its pzInsKey identifier. For example:

Queue entry not yet started upon by load activity (or a small chance it failed), Proceeding to load in user thread. DP Declare_AuthPolicies whoseinsKey is RULE-DECLARE-PAGES DECLARE_AUTHPOLICIES

Reason for the alert

A findPage request was made, but the system canceled the background thread because it did not (or could not) start the loader activity in time to process the request. Locate the code that submits the request to load the page to the background requestor and the calls to find the page. Reposition the code so that there is enough time for the background thread to pick up the job for processing.

Additional information

Alerts for asynchronous data page processing

Performance alerts, security alerts, and AES

Alert log message data


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.