Ahhh, the tangled webs we weave...

-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Bill
Anderson
Sent: Thursday, April 29, 2004 2:40 PM
To: [EMAIL PROTECTED]
Subject: Re: TCP error


The CSS I mention below sits behind a PIX. It took the network group some
time to figure out if it was the PIX or the CSS (or even possibly somewhere
out on the WAN). In our case (we are an AIX shop) it was most definitely not
the PIX. That don't mean a PIX can't do such things, but a PIX was a part of
the original problem set and was ruled out.


good luck

Bill Anderson
SITA Atlanta, GA
Standard Messaging Engineering
WebSphere MQ Service Owner
770-303-3503 (office)
404-915-3190 (cell)
[EMAIL PROTECTED]
http://www.mconnect.aero/



                      [EMAIL PROTECTED]
                      .AU                      To:
[EMAIL PROTECTED]
                      Sent by: MQSeries        cc:
                      List                     Subject:  Re: TCP error
                      <[EMAIL PROTECTED]
                      N.AC.AT>


                      04/28/2004 04:18
                      PM
                      Please respond to
                      MQSeries List






Thanks for the many responses!

Our MQ servers are behind a PIX firewall in a special DMZ, The clients all
run the same application and it is written using the C++ library and
disconnect is the last thing called before the app terminates.

Also, each object that creates a connection should close the connection when
the object gets cleaned up.

The information from Bill, show below looks very interesting, does the PIX
firewall series do this ?


Sid




-----Original Message-----
From: Bill Anderson [mailto:[EMAIL PROTECTED]
Sent: Thursday, 29 April 2004 12:41 AM
To: [EMAIL PROTECTED]
Subject: Re: TCP error


Don't be so quick to judge the MQ server as the problem. We just recently
resolved that (almost) exact problem on AIX. The error code for AIX is
AMQ9208, but it is still a tcp/ip reset. We tracked the problem down to a
CSS router (Cisco equipment), not the MQ server. The CSS was reclaiming
inactive tcp socket connections at an alarming rate and reeking havoc with
my MQ servers. To make matters worse, it has a rather complex algorithm for
determining if and when to send a reset. If it has plenty of resources
available for new connections it may leave things alone. but when the system
is busy, look out! cuz its going to get real stingy and kill off anything
that has been idle for much less time than a heartbeat interval.

I know that don't solve your problem, but you may want to look beyond the MQ
server.

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