We have been using runmqlsr. In some instances, the listener could be killed by a badly coded client application. The developer said that if he encountered an un-handled exception, the listener would die. And he demonstrated! I moved his server connection to a Windows box ,and haven't had any listeners disappear since. But another time, my Win2K workstation running Explorer got hosed, and I had to bring it down with the BRS. All 3 listeners on HP died at that moment. (2 on the test boz, 1 on the production box)
Looks like the interface between the listener and the command server has a bad line or two of code...at least on MQ 5.2 for HP. Bill -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Gordon Wang Sent: Friday, April 16, 2004 4:14 PM To: [EMAIL PROTECTED] Subject: Re: Listener dying on HPUX We had this before. We stopped QM and cleanup Shared Memory and Semophores and restarted. Gordon Wang -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of MCSHEFFREY, MICHELLE (SBCSI) Sent: April 16, 2004 3:35 PM To: [EMAIL PROTECTED] Subject: Re: Listener dying on HPUX We saw this vanishing listener problem when we tried using the MQ listener, prompting us to remain with inetd. We haven't tried the MQ listener with 5.3, so I don't know if it's still a problem. -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Thomas, Don Sent: Friday, April 16, 2004 2:07 PM To: [EMAIL PROTECTED] Subject: Re: Listener dying on HPUX Are you using runmqlsr or inetd? Don Thomas EDS - PASC * Phone: +01-412-893-1659 Fax: 412-893-1844 * mailto:[EMAIL PROTECTED] -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Beinert, William Sent: Thursday, April 15, 2004 4:45 PM To: [EMAIL PROTECTED] Subject: Listener dying on HPUX Three times today the listener just up and vanished on me. No error messages, no FDC files, no nothing. Just silence, followed by a barrage of phone calls and e-mails as monitors and users notice the problem. I am tempted to run a little shell script that checks to see if the thing is running every 2 minutes, while I prepare to upgrade from 5.2 to 5.3 (hoping that will make the problem go away). Has anyone seen something like this? Will a trace help to see what is happening? Bill Beinert Systems Programming Con Edison (212) 460-4853 When they took the fourth amendment, I was quiet because I didn't deal drugs! When they took the sixth amendment, I was quiet because, I was innocent. When they took the second amendment, I was quiet because I didn't own a gun! Now they've taken the first amendment, and I can say (or do) nothing about it. The Second Amendment is in place in case they ignore the others. MODWN DAbE 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 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 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
