WCCIL00event - SYS/SEVERE - MsgQueueContainer, appendMsg, MSG Limit exceeded - Over the limit 100000 for connection

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.

WCCIL00event (0), 2011.11.21 11:43:55.042, SYS, SEVERE, 54, Unexpected state, MsgQueueContainer, appendMsg, MSG Limit exceeded - Over the limit 100000 for connection (SYS: 1 Ctrl -num 2 CONN: 1)!Current queuesize: 113679

WCCIL00event (0), 2011.11.21 11:44:02.513, SYS, INFO, 54, Unexpected state, MsgQueueContainer, appendMsg, MSG Limit
exceeded - Going below message limit 100000 for connection (SYS: 1 Ctrl -num 2 CONN: 1)

Log-message with symbolic names:

WCCIL00event (0), <TIMESTAMP>, SYS, SEVERE, 54, Unexpected state, MsgQueueContainer, appendMsg, MSG Limit exceeded - Over the limit <current limit> for connection (SYS: <systemnumber> <manager-ID> -num <manager-number> CONN: <connection>)!Current queuesize: <queuesize>

WCCIL00event (0), <TIMESTAMP>, SYS, INFO,
54, Unexpected state, MsgQueueContainer, appendMsg, MSG Limit
exceeded - Going below message limit <current limit> for connection
(SYS: <systemnumber> <manager-ID> -num <manager-number> CONN: <connection>)

This log message describes that the current limit for the message queue in the receive direction has been exceeded. The current value for the queue size is written at the <queuesize> keyword. The <manager ID> and <manager number> keywords shows which connection has exceeded the limit. If the queue size falls below the specified limit within a defined period of time, the second log message is displayed. Otherwise the connection to the respective manager will be interrupted. The queue size and timeout can be defined with the EVENT manager config entries maxInputMsgCount and msgQueueLimitTimeout.

For more details, see the WinCC OA online help and search for the keywords "fault tolerance" and "stability".