Re: Connection error
TNX!!! From: Ruzi R <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Connection error Date: Mon, 10 May 2004 14:26:14 -0700 Hi Bobbee, We have been getting this error quite frequently on certain W2K/MQ 5.3 servers. I have posted this error on the list a couple of times -- along with some other people. As far as I remeber 2 things were suggesgted that are worth looking into: 1- Applications are not not terminationg gracefully (i.e. wothout DISCONNECTing) 2- Configuration problem on the server (e.g machine NIC, router,gateway and other network related setup). Our network people are in the process of looking into this prob. If I find anything I will post. I am also interested in any suggestions/ideas other than the two mentioned above. Regards, Ruzi --- Pavel Tolkachev <[EMAIL PROTECTED]> wrote: > Hello Bobbee, > > I believe this means that the client machine closes > the socket (I guess, preliminary, from the > application protocol (MQI over TCP) point of view). > > Hope this will help, > Pavel > > > > > > Robert Broderick > <[EMAIL PROTECTED] To: > [EMAIL PROTECTED] > OTMAIL.COM> cc: > Sent by: MQSeries > Subject: Connection error > List > <[EMAIL PROTECTED] > .AC.AT> > > > 05/10/2004 10:54 > AM > Please respond to > MQSeries List > > > > > > > I am getting "mucho" of the following. Anything I > should look at ??. Is > this where the client machine just ends the > session?? > > > bobbee > 05/10/04 09:24:38 > AMQ9208: Error on receive from host xx.xx.xx.xxx. > (TCP/IP was a client > machine) > > EXPLANATION: > An error occurred receiving data from xx.xx.xx.xxx > (This was a client > machine) over TCP/IP. This may be due to a > communications failure. > ACTION: > The return code from the TCP/IP (read) call was 73 > (X'49'). Record these > values > and tell the systems administrator. > > #define ECONNRESET 73 /* Connection reset > by peer */ > > _ > MSN Toolbar provides one-click access to Hotmail > from any Web page FREE > download! > http://toolbar.msn.com/go/onm00200413ave/direct/01/ > > 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 > > > > > > -- > > This e-mail may contain confidential and/or > privileged information. If you are not the intended > recipient (or have received this e-mail in error) > please notify the sender immediately and destroy > this e-mail. Any unauthorized copying, disclosure or > distribution of the material in this e-mail is > strictly forbidden. > > 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 _ Watch LIVE baseball games on your computer with MLB.TV, included with MSN Premium! http://join.msn.com/?page=features/mlb&pgmarket=en-us/go/onm00200439ave/direct/01/ 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
Re: Connection error
This may be true. The IP addresses line up with the people using MO71 and client puts to do messaging for testing. I am following up on the problem From: Pavel Tolkachev <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Connection error Date: Mon, 10 May 2004 12:27:49 -0400 Hello Bobbee, I believe this means that the client machine closes the socket (I guess, preliminary, from the application protocol (MQI over TCP) point of view). Hope this will help, Pavel Robert Broderick <[EMAIL PROTECTED]To: [EMAIL PROTECTED] OTMAIL.COM> cc: Sent by: MQSeries Subject: Connection error List <[EMAIL PROTECTED] .AC.AT> 05/10/2004 10:54 AM Please respond to MQSeries List I am getting "mucho" of the following. Anything I should look at ??. Is this where the client machine just ends the session?? bobbee 05/10/04 09:24:38 AMQ9208: Error on receive from host xx.xx.xx.xxx. (TCP/IP was a client machine) EXPLANATION: An error occurred receiving data from xx.xx.xx.xxx (This was a client machine) over TCP/IP. This may be due to a communications failure. ACTION: The return code from the TCP/IP (read) call was 73 (X'49'). Record these values and tell the systems administrator. #define ECONNRESET 73 /* Connection reset by peer */ _ MSN Toolbar provides one-click access to Hotmail from any Web page FREE download! http://toolbar.msn.com/go/onm00200413ave/direct/01/ 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 -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. 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 _ Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage! http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1/go/onm00200362ave/direct/01/ 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
Re: Connection error
That is some interesting information concerning the router and your
workaround. I believe the problem is the disconnect by the client
application accessing MQ. I know the people ar using MO71. BUt I am putting
your explanation in my save file so when I find out it is not that after I
get done invest. I have another route to follow.
Thank you very much for the explanation.
bobbee
From: Bill Anderson <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Connection error
Date: Mon, 10 May 2004 16:21:29 -0400
Tell us more about your system Window ?, UNIX ? Mainframe ? . and your
net work. I recently had a the same / similar problem you are having. I was
getting 300 + 9208 errors a day.
We are an AIX shop with CISCO routers and firewalls. (a CSS and a PIX). the
CSS turned out to be the culprit. It was designed for web type applications
I believe (so why the hell did we put an MQ server behind it?... not my
choice). Anyway, it was killing off MQ connection left and right by sending
a TCP/IP reset commands to inactive sessions. To make things really tough
to debug, it has a fairly complex algorithm for determining if and when to
clean up a connection. If it has lots of available resources for more
connections, it may leave an idle connection alone. However, when it begins
to "get busy" and resources are in short supply, it will start reaping idle
connections at an alarming rate.
Fortunately it is configurable, and we can set a given port to "flow
perminate" and that makes the problem go away for that port. Unfortunately,
you can only configure 20 ports in such a way. It won't take long before we
exceed 20 different ports that my MQ server has to talk to, so a more long
term solution needs to be found.
With more information, the group may be able to drive you closer to a
solution for your environment. But for what its worth... I feel your pain.
It took us a long time to figure out what was causing the rests on our
system. That nearly cost us a very important customer. See the list below
for thing to do that will help MQ cope with the problem with relative
grace.
In your qm.ini file implement the following options
Channels:
AdoptNewMCA= ALL
AdoptNewMCATimeout=60
AdptpNewMCACheck=All
When a reset is issued at the session layer, the pour receiver channel is
most likely left hanging. That is to say, it was never informed the session
was terminated. Heartbeats will eventually "unblock" it, but that, by
default will take about 6 minuets. The Channel stanzas above will instruct
the receiver to accept a new request for connection even though it thinks
it has a valid current socket connection. The AdoptNewMCATimeout=60 is not
necessary, because that is the default. I like to put it in there to make
it obvious to the untrained eye that the value exists. The AdoptNewMCACheck
stanza is a safeguard against a denial of service attack. It checks that
the new request for connection is coming from the same IP, channel name,
and queue manager name associated with the existing socket connection.
Hope some of this helps
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/
Robert Broderick
<[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
OTMAIL.COM> cc:
Sent by: MQSeries Subject: Connection error
List
<[EMAIL PROTECTED]
.AC.AT>
05/10/2004 10:54
AM
Please respond to
MQSeries List
I am getting "mucho" of the following. Anything I should look at ??. Is
this where the client machine just ends the session??
bobbee
05/10/04 09:24:38
AMQ9208: Error on receive from host xx.xx.xx.xxx. (TCP/IP was a client
machine)
EXPLANATION:
An error occurred receiving data from xx.xx.xx.xxx (This was a client
machine) over TCP/IP. This may be due to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 73 (X'49'). Record these
values
and tell the systems administrator.
#define ECONNRESET 73 /* Connection reset by peer */
_
MSN Toolbar provides one-click access to Hotmail from any Web page FREE
download! http://toolbar.msn.com/go/onm00200413ave/direct/01/
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 avail
Re: Connection error
Hi Bobbee, We have been getting this error quite frequently on certain W2K/MQ 5.3 servers. I have posted this error on the list a couple of times -- along with some other people. As far as I remeber 2 things were suggesgted that are worth looking into: 1- Applications are not not terminationg gracefully (i.e. wothout DISCONNECTing) 2- Configuration problem on the server (e.g machine NIC, router,gateway and other network related setup). Our network people are in the process of looking into this prob. If I find anything I will post. I am also interested in any suggestions/ideas other than the two mentioned above. Regards, Ruzi --- Pavel Tolkachev <[EMAIL PROTECTED]> wrote: > Hello Bobbee, > > I believe this means that the client machine closes > the socket (I guess, preliminary, from the > application protocol (MQI over TCP) point of view). > > Hope this will help, > Pavel > > > > > > Robert Broderick > <[EMAIL PROTECTED] To: > [EMAIL PROTECTED] > OTMAIL.COM> cc: > Sent by: MQSeries > Subject: Connection error > List > <[EMAIL PROTECTED] > .AC.AT> > > > 05/10/2004 10:54 > AM > Please respond to > MQSeries List > > > > > > > I am getting "mucho" of the following. Anything I > should look at ??. Is > this where the client machine just ends the > session?? > > > bobbee > 05/10/04 09:24:38 > AMQ9208: Error on receive from host xx.xx.xx.xxx. > (TCP/IP was a client > machine) > > EXPLANATION: > An error occurred receiving data from xx.xx.xx.xxx > (This was a client > machine) over TCP/IP. This may be due to a > communications failure. > ACTION: > The return code from the TCP/IP (read) call was 73 > (X'49'). Record these > values > and tell the systems administrator. > > #define ECONNRESET 73 /* Connection reset > by peer */ > > _ > MSN Toolbar provides one-click access to Hotmail > from any Web page FREE > download! > http://toolbar.msn.com/go/onm00200413ave/direct/01/ > > 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 > > > > > > -- > > This e-mail may contain confidential and/or > privileged information. If you are not the intended > recipient (or have received this e-mail in error) > please notify the sender immediately and destroy > this e-mail. Any unauthorized copying, disclosure or > distribution of the material in this e-mail is > strictly forbidden. > > 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
Re: Connection error
Tell us more about your system Window ?, UNIX ? Mainframe ? . and your net work. I recently had a the same / similar problem you are having. I was getting 300 + 9208 errors a day. We are an AIX shop with CISCO routers and firewalls. (a CSS and a PIX). the CSS turned out to be the culprit. It was designed for web type applications I believe (so why the hell did we put an MQ server behind it?... not my choice). Anyway, it was killing off MQ connection left and right by sending a TCP/IP reset commands to inactive sessions. To make things really tough to debug, it has a fairly complex algorithm for determining if and when to clean up a connection. If it has lots of available resources for more connections, it may leave an idle connection alone. However, when it begins to "get busy" and resources are in short supply, it will start reaping idle connections at an alarming rate. Fortunately it is configurable, and we can set a given port to "flow perminate" and that makes the problem go away for that port. Unfortunately, you can only configure 20 ports in such a way. It won't take long before we exceed 20 different ports that my MQ server has to talk to, so a more long term solution needs to be found. With more information, the group may be able to drive you closer to a solution for your environment. But for what its worth... I feel your pain. It took us a long time to figure out what was causing the rests on our system. That nearly cost us a very important customer. See the list below for thing to do that will help MQ cope with the problem with relative grace. In your qm.ini file implement the following options Channels: AdoptNewMCA= ALL AdoptNewMCATimeout=60 AdptpNewMCACheck=All When a reset is issued at the session layer, the pour receiver channel is most likely left hanging. That is to say, it was never informed the session was terminated. Heartbeats will eventually "unblock" it, but that, by default will take about 6 minuets. The Channel stanzas above will instruct the receiver to accept a new request for connection even though it thinks it has a valid current socket connection. The AdoptNewMCATimeout=60 is not necessary, because that is the default. I like to put it in there to make it obvious to the untrained eye that the value exists. The AdoptNewMCACheck stanza is a safeguard against a denial of service attack. It checks that the new request for connection is coming from the same IP, channel name, and queue manager name associated with the existing socket connection. Hope some of this helps 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/ Robert Broderick <[EMAIL PROTECTED]To: [EMAIL PROTECTED] OTMAIL.COM> cc: Sent by: MQSeries Subject: Connection error List <[EMAIL PROTECTED] .AC.AT> 05/10/2004 10:54 AM Please respond to MQSeries List I am getting "mucho" of the following. Anything I should look at ??. Is this where the client machine just ends the session?? bobbee 05/10/04 09:24:38 AMQ9208: Error on receive from host xx.xx.xx.xxx. (TCP/IP was a client machine) EXPLANATION: An error occurred receiving data from xx.xx.xx.xxx (This was a client machine) over TCP/IP. This may be due to a communications failure. ACTION: The return code from the TCP/IP (read) call was 73 (X'49'). Record these values and tell the systems administrator. #define ECONNRESET 73 /* Connection reset by peer */ _ MSN Toolbar provides one-click access to Hotmail from any Web page FREE download! http://toolbar.msn.com/go/onm00200413ave/direct/01/ 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
Re: Connection error
Hello Bobbee, I believe this means that the client machine closes the socket (I guess, preliminary, from the application protocol (MQI over TCP) point of view). Hope this will help, Pavel Robert Broderick <[EMAIL PROTECTED]To: [EMAIL PROTECTED] OTMAIL.COM> cc: Sent by: MQSeries Subject: Connection error List <[EMAIL PROTECTED] .AC.AT> 05/10/2004 10:54 AM Please respond to MQSeries List I am getting "mucho" of the following. Anything I should look at ??. Is this where the client machine just ends the session?? bobbee 05/10/04 09:24:38 AMQ9208: Error on receive from host xx.xx.xx.xxx. (TCP/IP was a client machine) EXPLANATION: An error occurred receiving data from xx.xx.xx.xxx (This was a client machine) over TCP/IP. This may be due to a communications failure. ACTION: The return code from the TCP/IP (read) call was 73 (X'49'). Record these values and tell the systems administrator. #define ECONNRESET 73 /* Connection reset by peer */ _ MSN Toolbar provides one-click access to Hotmail from any Web page FREE download! http://toolbar.msn.com/go/onm00200413ave/direct/01/ 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 -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. 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
Connection error
I am getting "mucho" of the following. Anything I should look at ??. Is this where the client machine just ends the session?? bobbee 05/10/04 09:24:38 AMQ9208: Error on receive from host xx.xx.xx.xxx. (TCP/IP was a client machine) EXPLANATION: An error occurred receiving data from xx.xx.xx.xxx (This was a client machine) over TCP/IP. This may be due to a communications failure. ACTION: The return code from the TCP/IP (read) call was 73 (X'49'). Record these values and tell the systems administrator. #define ECONNRESET 73 /* Connection reset by peer */ _ MSN Toolbar provides one-click access to Hotmail from any Web page FREE download! http://toolbar.msn.com/go/onm00200413ave/direct/01/ 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
