21

What is the difference between a dead letter Queue and a back out queue?

In WebSphere MQ terms and in terms of Application Servers.

All J2EE/JEE app servers have a MQ Provider do they also have a construct of a Dead Letter Queue or is that something specific to WebSphere MQ?

My understanding of a back out queue is as follows:

If MQ is unable to deliver the message to a destination after a specified number of attempts it moves the message to the back out queue.

I do not have a clear understanding of a Dead Letter queue.

Appreciate any assistance.

JoshMc
  • 10,239
  • 2
  • 19
  • 38
Manglu
  • 10,744
  • 12
  • 44
  • 57
  • https://community.ibm.com/community/user/imwuc/browse/blogs/blogviewer?BlogKey=28814801-083d-4c80-be5f-90aaaf81cdfb – Marek-A- Nov 27 '19 at 08:33

4 Answers4

16

The dead letter queue was always used in MQSeries (the last time I used MQ) to store messages that arrived at the queue manager but the queue didn't exist.

For example, if the message was address to queue manager X and queue Y, it would arrive via a channel at manager X.

If the receiver channel discovered there was no queue Y, it would be placed in the dead letter queue.

The backout queue, on the other hand, is more of an application-level thing (at least in terms of MQ). When an MQ client cannot process the message for some reason, it can back it out for later processing (back to it's original queue).

If it's backed out too many times (the threshold can be configured), it gets moved to the backout queue.

Muhammad Faizan Uddin
  • 1,339
  • 12
  • 29
paxdiablo
  • 854,327
  • 234
  • 1,573
  • 1,953
  • Here's more information: http://www.ibm.com/developerworks/websphere/library/techarticles/0803_titheridge/0803_titheridge.html – Miguel Ping Apr 03 '12 at 14:48
  • @paxdiablo, is this backout queue managed by the MQ manager or does the client have to connect to this queue ? – bluelurker Feb 04 '16 at 09:19
  • Although the back-out queue is managed by the queue manager, routing messages to a back-out queue is done by MQ's JMS and XMS client. – Shashi Jun 16 '16 at 08:26
4

Thanks for the answers. I also figured out that if the application is unable to move the message to the Back Out Queue (BOQ) for some reason, then an attempt is made to move the queue to the Dead Letter Queue (DLQ).

In our application it happened. There were some permission issues on the Back Out Queue, so the message could not be written to the BOQ and it ended up in the Dead letter Queue.

Dave DuPlantis
  • 6,378
  • 3
  • 26
  • 30
Manglu
  • 10,744
  • 12
  • 44
  • 57
2

The Dead Letter Queue behaves the same as a Backout. I treat the Dead Letter Queue as the Crematorium for messages that cannot be recovered in the Error or Backout queues and have some last, non-business specific data that need be collected. Once the info is captured, the message is put down for good. Backout is good for analyzing messages for data that may need to be recovered to completely reprocess or be sent back to an application area for them to decision on.

Wayne Hartman
  • 18,369
  • 7
  • 84
  • 116
0

A dead letter queue is also a local queue. If we trying to put a message from one queue to another queue and the message was not sent to the correct destination, at this time the meassage will go to a dead letter queue.

o-90
  • 17,045
  • 10
  • 39
  • 63
k.sekhar
  • 1