Posted: Thu Oct 10, 2002 12:03 pm Post subject: URGENT : trigger messages landing up the dead letter queue
Newbie
Joined: 08 Aug 2002 Posts: 6
the application that has to be triggered is already running.
the trigger type of the queue is First. but i find a lot of trigger messages generated and landing up the system dead letter queue.
1 doubt is y is there so many trigger messages generated when the application is already running.
2 doubt is y is these messages landing up the deadletter queue with a return code of MQFB_APPL_CANNOT_BE_STARTED
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
First, is your application designed to ever quit after it has been triggered, or just keep running forever? Normally, when you design an application to be triggered on type FIRST, you design it such that it processes all the messages on the queue, and once the queue depth goes to zero for a particular period of time (usually the wait interval on your MQGET) then you disconnect and quit. Since the queue depth has been reduced to zero, the next message that arrives will cause the trigger monitor to retrigger your application.
As far as why the trigger monitor sometimes isn't able to start your application, this is best debugged by running the trigger monitor in the foreground (runmqtrm) and watching the output to STDOUT. It is more verbose than what you can glean from the messages on the dead letter queue. _________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
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