WCCILevent - PARAM/SEVERE - recursion detected in sum alert use -dbg sumAlertCheck to get detailed information

Enclosed you'll find the explanation of a log-message which can be displayed during startup of the project. The log message is written to the PVSS_II.log-file.

WCCILevent (0), 2009.10.28 12:18:54.777, PARAM,SEVERE, 86, Invalid value, recursion detected in sum alert System1:mainpanels_geographical_overview_1.Warning. use -dbg sumAlertCheck to get detailed informations

Log-message with symbolic names:

WCCILevent (0), <TIMESTAMP>, PARAM,SEVERE, 86, Invalid value, recursion detected in sum alert <DPE-name> use -dbg sumAlertCheck to get detailed informations

This log message describes that indirect recursion was detected on summary alerts. The summary alert at the data point element <DPE-name> is deactivated in the EVENT manager. If direct recursion is detected, you will receive a similar log message listing the related summary alerts. A direct recursion is configured when the summary alert on a data point element DPE-A refers to the summary alert on DPE-B and vice versa.

In this case an indirect recursion is detected and therefore you need to use the mentioned debug level "-dbg sumAlertCheck" to get detailed information about the summary alert configured on the data point element <DPE name>.

In order to get detailed information,follow these steps:

  • Enable the debug flag "-dbg sumAlertCheck" for the EVENT manager.
  • Try to enable the summary alert for the data point element <DPE name>.
  • The summary alert information is written to the EVENT Manager log file PVSS00event0-log.
  • Disable the EVENT manager debug flag with "-dbg none".
  • Copy the file from the log directory of your project to another directory.
  • Open the file with a text editor.
  • Search for "DBGLEVEL=sumAlertCheck(49)" or "Recursion check for: <DPE name>" to jump to the beginning of the summary alert log output
  • The summary alert and the alerts assigned to it are listed.
  • Each level of the general alert is marked.
  • In the last line of the output you should see the data point element involved in the recursion.
  • Look for this data point element in the log output to find the cause of the recursion.

To resolve this issue, change the configuration of the summary alerts.