Queue-based error management

You can use the Message Reprocessing application to manage erroneous inbound and outbound asynchronous integration messages that use JMS queues.

Errors that occur when a message is sent from a queue to an external system are typically caused by a communication failure or a problem with database configuration when writing to interface tables or files. Errors that occur during inbound processing are typically a result of business rule validations or the inbound processing logic of the integration framework.

The sequential queue processes messages one at a time, in a first-in-first-out sequence. When the integration framework encounters an error in processing a message in a sequential queue, inbound or outbound, the error management mechanism is initiated and the message is flagged as having an error. Subsequent messages in the queue are not processed until the message in error is resolved or deleted. As a result, only a single error can exist in a sequential queue.

The continuous queue handles inbound processing only and processes messages in a multi-threaded mode. When an error occurs in the continuous queue, error management is initiated and the message is flagged as having an error. The integration framework continues to process subsequent messages in the queue. As a result, multiple errors can exist in a continuous queue.

Depending on your system configuration, the integration framework makes several attempts to reprocess the message, for either type of queue, before determining that an error requires intervention. The system also performs the following activities when encountering an error: