Yes and if you're in the middle of a transaction then it will have been/will get rolled back because the server connection channel agent process will eventually realise you're original connection will have failed.
Regards John Scott Senior Middleware Technical Specialist Argos Ltd -----Original Message----- From: Jim Ford [mailto:Jim_Ford@;MGIC.COM] Sent: 08 November 2002 15:38 To: [EMAIL PROTECTED] Subject: Re: Clients & Network "Glitches" There's no doubt that the network people are attempting an end-around. I just want to be prepared for it. Just to clarify: you get the TCP/IP "connect reset by peer" error as soon as the network burps. And this can't be tuned? There's no setting, either in Windows or in MQ, that can influence this? Also, besides reconnecting, the app would also have to reopen the queues, too, correct? Michael F Murphy/AZ/US/MQSo To: [EMAIL PROTECTED] lutions cc: <mmurphy@MQSOLUTI Subject: Re: Clients & Network "Glitches" ONS.COM> Sent by: MQSeries List <MQSERIES@AKH-WIE N.AC.AT> 11/08/2002 01:05 AM Please respond to MQSeries List As soon as your network burps, you get an "error receiving data from host" message on the client channel in the log and the channel is dropped. Once this happens, the handle to the queue manager is gone. Your application will get the 2009 the next time it tries to use that old object handle. Of course it needs to get a new handle so it needs to drop that connection and try again. Your network people are trying to redirect the root cause to you rather than themselves. I think they teach network people this routine in school because they all do it. Your application should be designed so when it gets a 2009 it just loops back to connect again, it doesn't need to end. If it can't connect, sleep for a minute or two and try again. Just keep doing this loop until you connect again. You may want to put a counter on it so you don't do it forever or you notify someone on support. There is no need to let the app die. With this method, there is no need for intervention. Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com Jim Ford <[EMAIL PROTECTED]> wrote: Date 11/07/2002 12:53:58 PM Recieved: To: [EMAIL PROTECTED] cc: Bcc Subject: Clients & Network "Glitches" We have many Windows NT clients that use our WAN to connect to Unix servers at our home office. Lately, our WAN has experienced numerous "glitches" (say our network guys), or "outages" (says me). When that happens, MQ returns a 2009 reason codes (MQRC_CONNECTION_BROKEN). Once this happens, all connection and object handles are invalid, so our applications are designed to respond by issuing a message like "network connection failed, please restart." The application then ends. Eventually, when the network is functional again, the restart and connect is successful and the app is usable again. The network support staff says that MQ should be more tolerant of these problems. That it should be able to "ride out" the problem, and then pick up where it left off. Setting aside the fact that hanging for 10 minutes isn't exactly an improvement over what we do now, I'm wondering what options we do have. When does MQ return the 2009 to the app? Is it immediately, or can this be tuned? What control (if any) do we have over this? 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 ********************************************************************** Click here to visit the Argos home page http://argos.co.uk The information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the intended addressee, any disclosure, reproduction, distribution, dissemination or use of this communication is not authorised. If you have received this message in error, please advise the sender by using your reply facility in youe e-mail software. All messages sent and received by Argos Ltd are monitored for virus, high risk file extensions, and inappropriate content. As a result users should be aware that mail maybe accessed. ********************************************************************** 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
