Jim,

When you get the 2009 depends on what your application is doing.  If you do
a GET with an extended wait, you may not get the 2009 until the channel
heartbeat interval cycle.  If the application does PUTs in response to user
input, you may not get the 2009 until the PUT happens.  It is only issued if
your application is exercising the MQ API and the API discovers that the
connectivity has been lost.

Furthermore, the nature of the client is that the client MCA is really a
process at the server that acts as a proxy for your client.  The 2009 is a
client response that indicates it can't reach the proxy but doesn't indicate
what the MCA did.  If the last action was a PUT or a GET, it may have
completed at the server - or not - you really don't know.  For this reason,
all client code is advised strongly to do everything under syncpoint.

Even if you do everything under syncpoint, the same consideration applies -
if you get a 2009 you don't know the outcome at the server.  For PUT and GET
this is not a problem because the transaction will be rolled back
(eventually).  If however you get a 2009 on the COMMIT, you really don't
know whether the transaction completed or not.

Finally, if you do leave an uncommitted transaction running when your
channel drops, you want to make sure that it eventually rolls back.  Be sure
to use heartbeat in the channel, and the KeepAlive and AdoptNewMCA in the
QM.ini.  Without proper tuning, your zombie client MCAs can hang around
forever and hold transactions open.  This can cause problems with log files
overflowing eventually as well as exceeding your max channels.

As far as your network guys contention that "MQ should be more tolerant of
these problems", they are half right.  MQ does a great job of tolerating
these problems if tuned correctly - and by MQ I mean the components IBM
supplies like the MCAs.  This is a case where it is the application that is
not tolerating the outages but the good news is that it sounds like it is a
homegrown application.  Getting vendors to fix their apps can be a
nightmare.

As someone else said in a previous post, the application should detect and
handle 2009 errors - and possibly others.  Some errors you can't do much
about and the app should probably report them and die (i.e. - 2012
ENVIRONMENT_ERROR).  Others like 2016 GET_INHIBITED may be transient in your
environment (if you regularly GET-inhibit queues to control application flow
for example) or they may indicate a permanent problem.  Once you decide
which error codes merit a disconnect and reconnect you can implement code to
survive the outage which will make you, your users and your network people
much happier.

-- T.Rob

-----Original Message-----
From: Jim Ford [mailto:Jim_Ford@;MGIC.COM]
Sent: Friday, November 08, 2002 10:38 AM
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

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

Reply via email to