Re: MQ issues with dead letter queue
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
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
Re: MQ issues with dead letter queue
It's clear you know Murphy's law :-) Now how about O'Reilly's law which states very simply: "Murphy was an optimist." Dave 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
Re: MQ issues with dead letter queue
Thanks Dave. We have on the proper fix and set the environmental variable via .profile. We had the PMR open for HP/UX since the second week of June. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of David Awerbuch Sent: Friday, July 02, 2004 10:18 AM To: [EMAIL PROTECTED] Subject: Re: MQ issues with dead letter queue Frank, Prasath, I did a search on www.ibm.com for the phrase MQFB_APPL_CANNOT_BE_STARTED. The first result returned is for the APAR reporting this problem. There are a number of PTF cover letters that include the fix for this APAR, depending on the platform you are on. If you have a PMR open with IBM, I am sure they told you to ensure that the applicable PTFs are installed on your target systems; if not, install them and attempt to reproduce the problem. One situation I ran into that caused this problem was an attempt to start the triggered application a second time, with the same process name (OpenVMS, the target system, didn't allow for this) and so the application failed to start. I had to modify the trigger definition to trigger FIRST, not EVERY, and modified the code to handle multiple passes until it exhausted the input queue. The code I was given to install was written to handle a single message, on the expectation of low messages volume. Our implementation suddenly starting triggering LOTS of times, and so we were operating outside the design specs for the original appl. Mr. Murphy was then reassigned to his next assignment :-). == David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] -Original Message- From: Bright, Frank [mailto:[EMAIL PROTECTED] Sent: Friday, July 02, 2004 9: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 = David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] 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
Re: MQ issues with dead letter queue
Frank, Prasath, I did a search on www.ibm.com for the phrase MQFB_APPL_CANNOT_BE_STARTED. The first result returned is for the APAR reporting this problem. There are a number of PTF cover letters that include the fix for this APAR, depending on the platform you are on. If you have a PMR open with IBM, I am sure they told you to ensure that the applicable PTFs are installed on your target systems; if not, install them and attempt to reproduce the problem. One situation I ran into that caused this problem was an attempt to start the triggered application a second time, with the same process name (OpenVMS, the target system, didn't allow for this) and so the application failed to start. I had to modify the trigger definition to trigger FIRST, not EVERY, and modified the code to handle multiple passes until it exhausted the input queue. The code I was given to install was written to handle a single message, on the expectation of low messages volume. Our implementation suddenly starting triggering LOTS of times, and so we were operating outside the design specs for the original appl. Mr. Murphy was then reassigned to his next assignment :-). == David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] -Original Message- From: Bright, Frank [mailto:[EMAIL PROTECTED] Sent: Friday, July 02, 2004 9: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 = David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] 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
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
Re: MQ issues with dead letter queue
Prasath, The export command has to be in the script that starts your trigger monitor, if I recall correctly. I had opened this PMR with IBM in 8/5/03 and IBM's solution fixed my problem. Also, I believe export MQ_SIGCHLD_SIGACTION=YES is incorrect. The other export command looks right. "BALAKRISHNAN, PRASATH (SBCSI)" <[EMAIL PROTECTED]> To Sent by: MQSeries [EMAIL PROTECTED] List cc <[EMAIL PROTECTED] n.AC.AT> Subject MQ issues with dead letter queue 07/01/2004 06:13 PM Please respond to MQSeries List <[EMAIL PROTECTED] n.AC.AT> 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 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
Re: MQ issues with dead letter queue
Most common causes are security problem, the path specfied in the applicid parameter, or the triggered application returning a non-zero return code. To get started, check the feedback code in the DLH for a reason. -Original Message- From: BALAKRISHNAN, PRASATH (SBCSI) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 01, 2004 3: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 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
