| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channel program ended abnormally |
« View previous topic :: View next topic » |
| Author |
Message
|
| SleeplessWithMQ |
 Posted: Fri Dec 08, 2006 9:07 am Post subject: Channel program ended abnormally |
 |
|
Newbie
Joined: 08 Dec 2006
Posts: 1
|
Our sender channels are going down abnormally.
The first error we see is:
12/07/2006 08:11:18 PM - Process(17811.1) User(mqm) Program(runmqchl)
AMQ9208: Error on receive from host 162 (162.XXX.XXX.XXX).
EXPLANATION:
An error occurred receiving data from 162 (162.XXX.XXX.XXX) over TCP/IP. This
may be due to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 104 (X'68'). Record these
values and tell the systems administrator.
The channels will end and then try to restart, this can continue for up to a couple of hours. Once it connects everything is good for a while.
Our network team saw FIN packets from the other end. Is there anyway to find out more information? |
|
| Back to top |
|
 |
| mvic |
| Posted: Fri Dec 08, 2006 9:28 am Post subject: Re: Channel program ended abnormally |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| SleeplessWithMQ wrote: |
EXPLANATION:
An error occurred receiving data from 162 (162.XXX.XXX.XXX) over TCP/IP. This
may be due to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 104 (X'68'). Record these
values and tell the systems administrator.
The channels will end and then try to restart, this can continue for up to a couple of hours. Once it connects everything is good for a while.
Our network team saw FIN packets from the other end. Is there anyway to find out more information? |
Assuming this is Linux, errno 104 is ECONNRESET. This is a common condition, which MQ will recover from, using Retry logic. Mostly the first place to look is any/all of the firewalls in the route between your channel programs. MQ channels will create long-lived TCP/IP connections, and some firewalls are configured to end long-running connections, regardless of the fact they are in use. This may or may not be the problem in your case - another possible reason is that someone tripped over the ethernet cable, and it got unplugged...
EDIT: Corrected to point out that MQ can recover using Retry. |
|
| 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
|
|
|
|
