|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
AMQ9208: Error on receive |
« View previous topic :: View next topic » |
Author |
Message
|
SAFraser |
Posted: Wed Jan 14, 2004 2:41 pm Post subject: AMQ9208: Error on receive |
|
|
 Shaman
Joined: 22 Oct 2003 Posts: 742 Location: Austin, Texas, USA
|
We have MQServer v5.2 on Solaris 8. In our dev environment, many developers use either the MQClient or the MQ Client for Java to connect to the server from their Windows workstations.
We get a lot of AMQ9208 errors like this one:
EXPLANATION:
An error occurred receiving data from <machine_name> (ip_address) over TCP/IP. This may be due to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 131 (X'83'). Record these values and tell the systems administrator.
The IP addresses are all from various developers' workstations. I've not been able to find an explanation for the TCP/IP return code. When I called one of these developers, he insisted he was not running anything at all that would be trying to connect to MQ. Hmmm....
I'm not sure where to go next, nor am I sure if it's something to be concerned about. But at a minimum, it sure is filling up our AMQERRxx.LOGs. Advice will be appreciated. Thank you very much. |
|
Back to top |
|
 |
csmith28 |
Posted: Wed Jan 14, 2004 3:16 pm Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
Most of the time this indicates a problem on the Client side. I see these all the time in on my AIX and SUN MQManagers and have learned to ignore them for the most part.
I hope your logging is set to CIRCULAR.
If you are not generating an abundance of .FDC files you prolly don't have much to worry about. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
JasonE |
Posted: Thu Jan 15, 2004 2:41 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
The tcpip return codes come from errno.h, and 131 on Solaris == ECONNRESET, which means the client side shut down the socket.
Normally this is an indication of a client app which doesnt MQDISC, or is killed / crashes etc. Either way its not a problem with the server |
|
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
|
|
|
|