| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| The return code from the TCP/IP (recv) call was 10054 |
« View previous topic :: View next topic » |
| Author |
Message
|
| pamorn |
 Posted: Tue Aug 28, 2007 10:25 pm Post subject: The return code from the TCP/IP (recv) call was 10054 |
 |
|
Newbie
Joined: 03 May 2006
Posts: 7
Location: Bangkok, Thailand
|
We have a WMQ6.0 server on W2k3 having sender&receiver channel paring with a remote queue manager on iSeries
We constantly receive these event error
# 1st event #
-------------------------------------------------------------------------------------
Source: WebSphere MQ
Error on receive from host ISERIES (10.xxx.xxx.xxx),
An error occured received data from ISERIES (10.xxx.xxx.xxx) 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.
-------------------------------------------------------------------------------------
# 2nd subsequence event #
-------------------------------------------------------------------------------------
Source: WebSphere MQ
Channel program ended abnormally
Channel program 'ISERIES.TO.W2K3' ended abnormally
Look at previous error messages for channel program
'ISERIES.TO.W2K3' in the error files to determine the cause of the failure
-------------------------------------------------------------------------------------
The 'ISERIES.TO.W2K3' channel stop immediately.
Any got experience on these errors? |
|
| Back to top |
|
 |
| markt |
| Posted: Tue Aug 28, 2007 10:32 pm Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
You did, of course, do a search for this return code before posting.
How many hits did you find? How many were relevant? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 29, 2007 12:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| markt wrote: |
You did, of course, do a search for this return code before posting.
How many hits did you find? How many were relevant? |
It's not like the question has been posted before or anything..... 
The Search Button Is Your Friend. Don't Fear The Search Button
(There's a song in there somewhere......  )
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pamorn |
| Posted: Wed Sep 26, 2007 3:29 am Post subject: |
|
|
Newbie
Joined: 03 May 2006
Posts: 7
Location: Bangkok, Thailand
|
Hi all,
I just recently revisited this problem, and fixed it by simply applying fix pack 6.0.2.1. I think this is special problem with Windows 2003R2. Thanks for all comments. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Sep 26, 2007 6:54 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
I completely disagree with pamorn's conclusion.
There is NOTHING in 6.0.2.1, Windows 2003 or any other platform, which has any bearing AT ALL on whether a channel receives 10054 (ECONNRESET) from the TCP layer. This error is generated externally from WMQ, and so upgrading can have no possible effect on the occurrence of the error. Sequence does not imply causality.
The probable reason for the error going away is that a temporary network problem has either been resolved by a hard-working and diligent network team, or, more likely, it has just gone away on its own following a reset of some hardware component.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
