We've been through this before. I don't see how anyone can run a large
scale MQSeries infrastructure without the use of a dead letter queue. If a
single queue becomes full or a single user is not authorized to a remote
queue, the channel will be stopped. This means that any other application
using the channel is out of the water until someone manually addresses the
problem. Not very practical in my opinion. I also don't understand why
use of a dead letter queue causes you problems with this product. The
actions of the DLQ handler are under your control. You can throw the
messages away or take any other action you want.
- Bruce Giordano
Jeff A Tressler <[EMAIL PROTECTED]>
To:
[EMAIL PROTECTED]
Sent by: MQSeries List cc:
<[EMAIL PROTECTED]> Subject: Dead Letter Queue
Friday September 26, 2003 02:17 PM
Please respond to MQSeries List
Hi, have many of you decided to NOT use a Dead Letter Queue? We are
looking into a product that uses MQSeries as a transport layer. The tool
assumes there is no DLQ.
What happens is it sets the Exception Report option so if the remote queue
if full, it returns an exception to the send portion of the tool. So if
there is a DLQ
and a DLQHandler running, the message may be recycled to the original queue
and processed but the sending side throws an exception.
Jeff Tressler
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
