As an alternative to the prconfig.xml file, you can use Dynamic System Settings to configure your application.See How to create or update a prconfig setting.
The alert indicates that a requestor's wait time to access to the rule assembly cache has exceeded a threshold.
Cache find synchronization time has exceeded threshold of 30 ms: 856 ms. Details: Total find time:
ELAPSED time = 1,712;
Synchronization time = 856;
Caller ActivityClassName = ;
Caller ActivityRuleSet time = ;
aFUA Aspect = Action;
aFUA Identification = Rule-Obj-Activity
Code-.SystemIndexer;aFUA Defining Class = Rule-Obj-Activity
You can modify the default settings in the alerts section of the prconfig.xml file, as follows:
prconfig.xml file and update these alerts sections:enabled
<env name = “alerts/fua/synchtime/enabled" value="true" />
The enabled value is a boolean. To turn off the alert, change the value to "false".
threshold
<env name = “alerts/fua/synchtime/threshold" value="30" />
The threshold value is a positive integer in milliseconds (default is 30 ms).
As an alternative to the prconfig.xml file, you can use Dynamic System Settings to configure your application.
See How to create or update a prconfig setting.
This alert indicates system loading issues. Related PEGA0037 and PEGA0001 alerts are likely, which merit investigation. Excessive cache synchronization times lead to longer assembly and interaction times.
|
alert log, prconfig.xml file, rule cache |
|
Understanding alerts |
SysAdmin category