What is the difference between a Dead Letter Queue and a back out Queue?

jakarta-ee jms ibm-mq
Manglu picture Manglu · May 18, 2009 · Viewed 41.2k times · Source

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.

Answer

paxdiablo picture paxdiablo · May 18, 2009

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.

Related questions

Accessing MQ with JMS

i am using MQ7 and trying to access a queue with JMS api's. Getting this error. Has anyone seen it before? How do i resolve this? TIA Exception in thread "main" com.ibm.msg.client.jms.DetailedJMSException: JMSFMQ6312: An exception …

Read More
Is it a good practice to use JMS Temporary Queue for synchronous use?

If we use JMS request/reply mechanism using "Temporary Queue", will that code be scalable? As of now, we don't know if we will supporting 100 requests per second, or 1000s of requests per second. The code below is what I …

Read More
Why is my JNDI lookup for a QueueConnectionFactory returning null?

I am trying to look up a QueueConnectionFactory and Queue via Geronimo's JNDI. The Queue gets returned fine, but the QueueConnectionFactory lookup always returns null. It doesn't throw a NamingException, which is what I'd expect if the JNDI name was …

Read More