|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Dead Letter Handler and Triggering |
« View previous topic :: View next topic » |
Author |
Message
|
mrlinux |
Posted: Mon Jul 29, 2002 7:24 am Post subject: |
|
|
 Grand Master
Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA
|
Post your queue definiton for your application. _________________ Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
Back to top |
|
 |
bduncan |
Posted: Mon Jul 29, 2002 10:20 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
|
Something doesn't sound quite right - you mentioned that the messages are going to the initiation queue? How do you know this? The trigger monitor should pick the messages up immediately. And if the trigger monitor isn't running correctly, the queue manager won't even put the trigger messages on the initiation queue.
Another thing I'd try is running the trigger monitor (runmqtrm) in the foreground and watch the output from it.
Also, post the related queue and process definitions like mrlinux suggested... _________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
Back to top |
|
 |
mgrabinski |
Posted: Mon Jul 29, 2002 9:49 pm Post subject: Triggering a Dead Letter Queue Handler |
|
|
Master
Joined: 16 Oct 2001 Posts: 246 Location: Katowice, Poland
|
If you are using the standard DLQ handler (runmqdlq), you may encounter problems, since the utility doesn't accept the MQTMC2 structure passed as parameter by the the trigger monitor. The structure contains information about queue that caused the ttrigger event and other data.
To get around this problem, you should write a piece of code that will be triggered. It should accept the triggering structure and call the DLQ Handler. _________________ Marcin Grabinski <>< |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Jul 30, 2002 7:43 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Is your DLHandler itself causing messages to go to the DLQ, causing it to loop on the same message? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|