| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channel Program ending abnormally |
« View previous topic :: View next topic » |
| Author |
Message
|
| muralidhar |
 Posted: Wed Apr 03, 2002 4:11 pm Post subject: |
 |
|
Acolyte
Joined: 28 Feb 2002
Posts: 50
|
In my error logs and windows event viewer, I am seeing AMQ9514 and AMQ9999 errors every 15 minutes. But channel is still active.
My MQServer v5.2 is on Windows 2000. Queue Manager on the other end is on OS/390.
Here are the error messages
04/01/2002 19:34:47
AMQ9514: Channel 'CHCHABCD.MM11' is in use.
EXPLANATION:
The requested operation failed because channel 'CHCHABCD.MM11' is currently
active.
ACTION:
Either end the channel manually, or wait for it to close, and retry the
operation.
-------------------------------------------------------------------------------
04/01/2002 19:34:47
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'CHCHABCD.MM11' ended abnormally.
ACTION:
Look at previous error messages for channel program 'CHCHABCD.MM11' in the
error files to determine the cause of the failure.
I set disconnect interval to '0' and Heartbeat interval to 300. The problem I am experiencing is for a Server Channel.
I request your suggestions.
Thanks,
Murali
|
|
| Back to top |
|
 |
| StefanSievert |
| Posted: Wed Apr 03, 2002 4:37 pm Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
Is that the name of your sender channel to the /390 or the name of the receiver channel?
Obviously something tries to perform a periodic action on the channel that requires the channel to be inactive (eg. START CHL, RESET CHL). Do you have any monitoring tools active on either NT or /390 that try to do something with the channel every 15 minutes?
If it's a receiver channel, it will be happening on the mainframe, if it's a sender, it will be on Win2k.
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| muralidhar |
| Posted: Thu Apr 04, 2002 9:05 am Post subject: |
|
|
Acolyte
Joined: 28 Feb 2002
Posts: 50
|
Hi Stefan,
The channel name I specified earlier is a server channel on Win2K. On Win2K we don't have any monitoring tools. I am not sure about monitoring tools on OS/390. Do you think is this something serious ? So far this is not causing any other problem.
Thanks,
Murali |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Thu Apr 04, 2002 11:10 am Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| Quote: |
On 2002-04-04 09:05, muralidhar wrote:
Hi Stefan,
The channel name I specified earlier is a server channel on Win2K. On Win2K we don't have any monitoring tools. I am not sure about monitoring tools on OS/390. Do you think is this something serious ? So far this is not causing any other problem.
Thanks,
Murali
|
Murali,
if it is a server channel, than you should look on the mainframe for something that does try to act on the requester channel every 15 minutes (remember, a server channel is initiated from the other end). If you could talk to your mainframe (MQ) guys if they use a monitoring product on /390 (Candle, BMC, etc.), you might be one step closer to find out why you get that message periodically.
I can't see a reason why this may cause a 'serious' problem.
Cheers,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| mrlinux |
| Posted: Thu Apr 04, 2002 11:40 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
The message indicates someone(or program) tried to start the channel after it was already started, I would look for something starting the channels such as trigger setting on the xmitq
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
[ This Message was edited by: mrlinux on 2002-04-04 11:40 ] |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Thu Apr 04, 2002 4:06 pm Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| Quote: |
On 2002-04-04 11:40, mrlinux wrote:
The message indicates someone(or program) tried to start the channel after it was already started, I would look for something starting the channels such as trigger setting on the xmitq
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
|
Jeff,
wouldn't an active channel mean that the XMITQ is open for input, thus avoiding a trigger message from being generated? If this message is generated regularly every 15 minutes, I'd rather suspect some monitoring tool as the cause. What do you think?
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| 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
|
|
|
|
