I've seen something similar at one of my clients. MQ Visual Edit (a beta version) in client mode was trying to get a JMS message that had a mal-formed RFH2 header. I guess that version of MQVE didn't handle the exception because runmqlsr would die. This was with MQ5.2 on Solaris, however. We didn't go back and test to see if it still happened in MQ5.3, or newer versions of MQVE.
... Jim Blake -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Beinert, William Sent: April 19, 2004 7:01 AM To: [EMAIL PROTECTED] Subject: Re: Listener dying on HPUX 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 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
