We have the start of the trigger monitor in our start up script for WMQ on
every box. We also have it crontabed to check if the trigger monitor is
running and restart if necessary. Since this check was based on time, it
would occasionally beat out the start trigger command within the MQ start-up
script we use. This is when we encountered all our problems on an
intermittent basis.
To test this solution, we shut down the trigger monitor (get disabled the
IQ) so it would be re-started via the crontab and an echo of the
environmental variable at the top of the script showed it was not set. Must
be a different shell or something causing the .profile exported variable not
to show up or be accessible by the crontabed script.
I took a call from a very kind individual who urged me to change the crontab
start trigger script. I won't use names as it might upset that individual or
the company he works for, but I do want thank him now. Thanks for the help!
Frank
-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Miller,
Dennis
Sent: Wednesday, July 07, 2004 1:29 PM
To: [EMAIL PROTECTED]
Subject: Re: MQ issues with dead letter queue
The trigger monitor calls upon features of the underlying OS to invoke the
triggered application. Of course, the specific mechanism varies completely
by platform/OS. MQFB_APPL_CANNOT_BE_STARTED is a catch-all that simply
reflects that the OS mechanism failed (or thinks it failed). To find the
exact reason sometimes takes a little patience--sometimes running the
triggered app synchronously, in foreground will reveal an explanatory
console message. Most common causes though, are an OS (as opposed to MQ)
authorization problem, application cannot be found (as in path error or typo
in applicid), or application returning non-zero RC (which gets passed back
to the trigger monitor).
Regards,
Dennis
-----Original Message-----
From: Bright, Frank [mailto:[EMAIL PROTECTED]
Sent: Friday, July 02, 2004 6:35 AM
To: [EMAIL PROTECTED]
Subject: Re: MQ issues with dead letter queue
I don't have the answer but we see it too.
We having trouble reproducing the error on our test system to trace it as
requested by IBM. It only occurs occasionally on some systems. X'109' or
MQFB_APPL_CANNOT_BE_STARTED is the MQDLH reason code.
Thanks
Frank
-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of
BALAKRISHNAN, PRASATH (SBCSI)
Sent: Thursday, July 01, 2004 6:13 PM
To: [EMAIL PROTECTED]
Subject: MQ issues with dead letter queue
Hello,
For the last several days we have been accumulating large numbers of
trigger messages in the Dead Letter Queue. We added this in the .profile
which was suggested in one of the forums as a possible solution
# For Web Sphere MQ 5.3 SP 4
export AMQ_SIGCHLD_SIGACTION=YES
export MQ_SIGCHLD_SIGACTION=YES
Still it did not work. Can you help me in finding a possible
solution
Thanks
Prasath Balakrishnan
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
-----------------------------------------
This e-mail message and any attachments contain confidential information
from Medco. If you are not the intended recipient, you are hereby notified
that disclosure, printing, copying, distribution, or the taking of any
action in reliance on the contents of this electronic information is
strictly prohibited. If you have received this e-mail message in error,
please immediately notify the sender by reply message and then delete the
electronic message and any attachments.
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
-----------------------------------------
This e-mail message and any attachments contain confidential information from Medco.
If you are not the intended recipient, you are hereby notified that disclosure,
printing, copying, distribution, or the taking of any action in reliance on the
contents of this electronic information is strictly prohibited. If you have received
this e-mail message in error, please immediately notify the sender by reply message
and then delete the electronic message and any attachments.
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
