WebSphere Message Brokers
File: ac12341_.dita
Writer: Kate Hostler

Reference topic

This build: July 31, 2007 21:18:26

Exceptions when dealing with unknown and timeout messages

When timeout messages or unknown messages from unknown timeout processing are produced from an AggregateReply node they originate from a internal queue and not from a MQInput node. This effects how the error handling should be performed.

If a message sent down the timeout thread causes an exception, the message rolls back to the AggregateReply node and is sent to the catch terminal. If this terminal is either unattached or an exception occurs while processing the message, the timeout is rolled back onto the internal queue and is reprocessed. Potentially, this will lead to an infinite loop which can only be stopped either by removing the timeout message from the internal queue (not recommended), or by deploying a version of the messages flow that fixes the problem.

To avoid this infinite loop take the following actions.

Note: The failure terminal is currently not used and messages will never be passed to this terminal.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:18:26

ac12341_.dita This topic's URL is: