2.5 Troubleshooting problems if processing of a jobnet with a start condition is delayed
In some cases, when a large number of events occur unexpectedly for a specific jobnet with a start condition, processing is delayed because large quantities of unprocessed data are stored on the event/action control manager. For example, an operation for an event job or a custom event job is delayed or an event job or a custom event job does not end quickly even if an event that matches the specified condition occurs.
The following shows the sequence from when a problem occurs in the system until the operator recognizes the problem:
-
A large number of events occur unexpectedly for a specific jobnet with a start condition.
-
The manager host slows down because there is too much data to be processed, causing other event jobs and custom event jobs to be held in queues or other problems to occur.
-
The event/action control manager outputs the KAVT0333-W message to the integrated trace log.
-
You receive the message output in step 3, and notice that a problem has occurred on the event/action control manager.
In such cases, you can end the delay by deleting the information contained in the event/action control manager.
When restoring the operating status, you can check information by using the Web GUI (Management Portal) or commands. The following sections describe these two methods.