PEGA0001 alert: HTTP interaction time exceeds limit
The PEGA0001 alert is generated when the elapsed time for an HTTP interaction time exceeds the threshold setting. This alert represents a single server interaction. The PEGA0069 alert, Client page load time, represents the total time to render a screen (multiple server interactions, network time, and browser processing).
Example message text
HTTP interaction has exceeded the elapsed time "alert" threshold of 1000 ms: 2066852 ms. request: http://sdevrulesb3:9081/prweb/PRServlet/ksjNgaBVLyUBsr9UytBwWg%5B%5B*/!Developer?pyActivity=WBSave
Default prconfig.xml settings
<env name="alerts/browser/interactionTimeThreshold/enabled" value="true" />
When set to “true,” the alert is enabled. When set to “false,” the alert is disabled.
<env name="alerts/browser/interactionTimeThreshold/excludeAssembly" value="true" />
Use this setting to exclude ("true") or include ("false") rule assembly time in the threshold result. Rules assembly (RA) occurs the first time that a particular rule is referenced. The Pega 7 Platform generates, compiles, loads, and runs the Java source code for a unique Java class. In an active production system, the already assembled Java class for a rule should be found by the system. When the class is not found, rules assembly continues to occur and compromise system performance.
Set the value to "false" if you suspect that assembly time is affecting the TimeThreshold result.
warnMS (where "MS" is milliseconds)
<env name="alerts/browser/interactionTimeThreshold/warnMS" value="1000" />
Specifies the threshold value in milliseconds. The default is 1 second.
Reasons for the alert
If your alert log contains a large number of PEGA0001 messages, a problem on the server might be causing a significant slowdown. Check the server for the underlying problem.
If the text message identifies an activity, the activity might be taking an extremely long time to process. Use the PAL performance tool or DBTrace to check which steps the activity is running.