Author |
Message
|
Simon McAlister |
Posted: Tue Sep 21, 2004 4:43 pm Post subject: return code from the TCP/IP (recv) call was 10054 (X'2746'). |
|
|
Novice
Joined: 05 May 2004 Posts: 11
|
I am getting this message whenever the channel tries to start
The return code from the TCP/IP (recv) call was 10054 (X'2746').
Does anyone know where I can find the TCP/IP return codes and their meanings. |
|
Back to top |
|
 |
siliconfish |
Posted: Tue Sep 21, 2004 5:03 pm Post subject: |
|
|
 Master
Joined: 12 Aug 2002 Posts: 203 Location: USA
|
TCP/IP Error 10054 : Connection reset by peer,
There could be a problem with your network connection. |
|
Back to top |
|
 |
csmith28 |
Posted: Tue Sep 21, 2004 5:14 pm Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
siliconfish wrote: |
TCP/IP Error 10054 : Connection reset by peer,
There could be a problem with your network connection. |
What OS is this?
On AIX "Connection reset by peer" is TCP/IP return code 73.
I are such confused. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
Simon McAlister |
Posted: Tue Sep 21, 2004 5:16 pm Post subject: |
|
|
Novice
Joined: 05 May 2004 Posts: 11
|
The OS is Windows 2000.
The communication is on a test environment with all queue managers on the same machine different ports. |
|
Back to top |
|
 |
siliconfish |
Posted: Tue Sep 21, 2004 5:24 pm Post subject: |
|
|
 Master
Joined: 12 Aug 2002 Posts: 203 Location: USA
|
Set the Environment variable MQNOREMPOOL=1 and try this may resolve your issue. |
|
Back to top |
|
 |
csmith28 |
Posted: Tue Sep 21, 2004 5:24 pm Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
um, ok
is there a listener process running for the MQManager in question? _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
srikad1 |
Posted: Thu Oct 14, 2004 3:42 am Post subject: |
|
|
Newbie
Joined: 14 Oct 2004 Posts: 2
|
Try sending a heart beat message every 15 minutes since this error happens after 2 hours of inactivity on the JMS server.
This would let it recycle the sockets and stops the timeouts. |
|
Back to top |
|
 |
Nigelg |
Posted: Mon Oct 18, 2004 1:21 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
MQNOREMPOOL only applies if runmqlsr is being used, and causes the RCVR/SRVCONN channels to run as threads in runmqslr instead of in amqrmppa. The variable also causes SDR type channels to run as threads in runmqchi instead of in amqrmppa.
Since the error msg has come from the TCP layer, there is clearly no point in varying anything in the WMQ environment as siliconfish suggested.
Indeed, this only encourages the view that there is some fault in WMQ. Don't shoot the messenger! |
|
Back to top |
|
 |
|