Automatically force a message flow to stop

Monitors message flow processing time and automatically takes a specified action if the timeout is exceeded.

About this task

Two message flow properties are provided to specify the maximum amount of time that any message flow can be allowed to process a message and an action to be taken if the timeout is exceeded:

processingTimeoutSec - maximum time a message flow can process a message before taking a specified action. The time is measured in seconds and is taken from the point a message is received on an input node.
processingTimeoutAction - the action to take. Currently, this action is restricted to none or restartExecutionGroup.

There are two ways that both of these properties can be set for a message flow:

Directly within a BAR file.
As one of the attributes within a workload management policy that is defined within Integration Registry.

BAR file

The two properties can be set in the following ways: :

Within the BAR file through the IBM® Integration Toolkit editor.
Within the BAR file through the mqsiapplybaroverride command line.

Workload management policy

Create and configure a workload management policy. For more information about workload management, see Workload management.

When the processingTimeoutSec timeout period is exceeded, an event message is published. For more information, see Message flow timeout exceeded event message. Thereafter, if the processingTimeoutAction option has been set to none and processing of the message flow continues to completion, another event message is published. For more information, see Message flow processing finished event message. However, if the processingTimeoutAction option has been set to restartExecutionGroup the integration server is restarted and no further event messages are published from the message flow.