| Author |
Message
|
| offshore |
 Posted: Tue Feb 04, 2003 10:44 am Post subject: Connection Reset By Peer??? |
 |
|
Master
Joined: 20 Jun 2002
Posts: 222
|
All,
I have a question concerning an error message I am receiving on our MVS channel initator log.
The error message is:
+CSQX208E +QM1 CSQXRESP Error receiving data,
connection HostName (IP.Address),
TRPTYPE=TCP RC=00000461
The RETURN CODE=0461 is Communication Reset By Peer.
We also receive a similar error message on the Windows 2K MQ:
SOURCE MQSERIES
EVENT ID 9208
Error on receive from host HostName (IP.Address).
An error occurred receiving data from HostName (IP.Address) over TCP/IP. This may be due to a communications failure.
The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these values and tell the systems administrator.
Specs
MQ 2.1 for OS/390
MQ 5.2.1 for Windows 2000
The channels seem to recover OK, as messages begin passing, etc...
My question(s) is
1) Is this a network problem (ie..switch/router/firewall...)
2) Is the a MQ problem and if so where?? -MVS or W2k-
3) What exactly is connection reset by peer???
Any help would be appreciated....TIA!! |
|
| Back to top |
|
 |
| yaakovd |
| Posted: Wed Feb 05, 2003 8:35 am Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
This is clear TCP problem.
There is 2 cases when it happens:
1 Remote machine went down.Sender channels still running. KeepAlive probes are sent,no reply received.Sender channel ends abnormally.
2 Remote machine went down and came back.Sender channels still running.An application tries to send data through the channel. Remote TCP stack sends reset, as the connection no longer exists. Local Sender channel ends abnormally.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
| offshore |
| Posted: Wed Feb 05, 2003 12:31 pm Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
Both machines received the error on receive at the same time. I'm thinking it must be in the routers.
As far the machines going down...The Win2K machine didn't and I know the MVS machine didn't.
Looking the the logs of TCP on MVS there is nothing to indicate that there was an issue w/ TCPIP on the mainframe. Looking on the W2K event viewer there wasn't anything to indicate there was a problem.
Maybe it was just small enough to disrupt MQ????
Anyone else have ideas???? |
|
| Back to top |
|
|
| ukusdxw |
| Posted: Wed Jul 30, 2003 1:44 am Post subject: Same problem |
|
|
Newbie
Joined: 30 Jul 2003
Posts: 1
|
I have exactly the same setup regards OS/390 talking to Windows and I'm experiencing the same errors. We have logged the problem with IBM who suggested it might be the MTU size on the Windows Server. This was altered, but to no avail.
Have you had any joy in resolving this problem since you last posted this message? |
|
| Back to top |
|
|
| offshore |
| Posted: Thu Sep 11, 2003 12:08 pm Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
With a little help from IBM here is the solution<
Edit CSQ4XPRM in parmlib.
Add/change ADOPTMCA and ADOPTCHK under the CSQ6CHIP heading.
(portion shown below:)
CSQ6CHIP
ADOPTMCA=YES, ADOPT MCA OPTION
ADOPTCHK=ALL, ADOPT CHECK OPTION
After making the changes, run the job to assmble and link the member.
I was also recommened to apply PTF UQ61044. Some sites have had trouble with CHIN hanging when trying to bring down MQ Series.
HTH |
|
| Back to top |
|
|
| RatherBeGolfing |
| Posted: Wed Oct 15, 2003 2:43 pm Post subject: |
|
|
Centurion
Joined: 12 Nov 2002
Posts: 118
Location: Syracuse, NY, USA
|
My $.02 on this. We have exactly the same setup as well, we have applied UQ61044 and set ADOPTMCA=YES, ADOPTCHK=ALL and we STILL have the problem with TCP rc 461. In fact, we're in the middle of it right now!
As others have said, the channels seem to repair themselves, but during the "sluggishness" some of our real time web-->legacy app transactions time out.
We're heading to V5.3 in production this coming Sunday, and haven't seen any of this stuff in our Test and QA environments....only 3 more days!
Cheers! |
|
| Back to top |
|
|
|
|
