| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| How to avoid msgs not landing onto DLQ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| exerk |
 Posted: Fri Oct 16, 2009 12:17 am Post subject: |
 |
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Mr Butcher wrote: |
if you do not want messages to be routed to the DLQ, rmove it from the qmgr DEADQ attribute. if your local queue on remote qmgr becomes full, channels will be stopped / retry as messages can not be delivered (assuming persistence and npmspeed stuff as discussed many times before), and they will pile up on the SCTQ. if that one is full too, the sending application will get the 2053 again. (if this is fine for you and is handled by the application, as it already gets the 2053 for the "local" target queue).
there are pros aond cons about running without dlq, but i do not want to start this discussion here. |
To augment Mr Butcher's suggestion, define a separate cluster and put an MCAUSER in the CLUSRCVR channels, and ensure the userid does NOT have access to the dead-letter queue, and put the queues in that cluster, which should then prevent any impact on other channels.
Next time your app team have such a stellar idea, ensure there is WMQ Admin representation at the meeting. That way you can nip in the bud any such idiocy, and state what it is you have to do to mitigate such 'design', and how much it will cost (in support terms).
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
 |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
