How do I dequeue from an exception queue?
The exception queue for a multiconsumer queue must also be a multiconsumer queue. Expired messages in multiconsumer queues cannot be dequeued by the intended recipients of the message. However, they can be dequeued in the REMOVE mode once (only once) using a NULL consumer name in dequeue options. Messages can also be dequeued from an exception queue by specifying the message ID. Expired messages can be dequeued only by specifying message ID if the multiconsumer exception queue was created in a queue table without the compatible parameter or with the compatible parameter set to ‘8.
The exception queue for a multiconsumer queue must also be a multiconsumer queue. Expired messages in multiconsumer queues cannot be dequeued by the intended recipients of the message. However, they can be dequeued in the REMOVE mode once (only once) using a NULL consumer name in dequeue options. Messages can also be dequeued from an exception queue by specifying the message ID.
Related Questions
- After a message has been moved to an exception queue, is there a way, using SQL or otherwise, of identifying which queue the message resided in before moving to the exception queue?
- Why are messages moved to the default AQ exception queue upon propagation failures for an outbound propagation job?
- How do I dequeue from an exception queue?
