Author |
Message
|
ms_mq |
Posted: Tue Sep 04, 2007 5:01 am Post subject: MQ channel issue |
|
|
Acolyte
Joined: 23 Feb 2007 Posts: 69
|
Hi ,
Could anyone help me out on this issue please ?
The sender channel from one of our production application server is going to
retrying state very frequently. It shows status as RUNNING for a while and then
immediately it goes to retry state.
The Queue manager and other channels on the remote servers are running fine .
Iam able to ping the remote server , traceroute , telnet on the MQ port etc
without any issues from the source server.
AMQ Error message at the source :
9/4/2007 18:17:25 - Process(4576.1) User(mqsvcprj1) Program(runmqchl.exe)
AMQ9558: Remote Channel is not currently available.
EXPLANATION:
The channel program ended because the channel 'PGMAPP1.T.PGMAPP2' is not
currently available on the remote system. This could be because the channel is
disabled or that the remote system does not have sufficient resources to run a
further channel.
ACTION:
Check the remote system to ensure that the channel is available to run, and
retry the operation.
----- amqrfpta.c : 340 --------------------------------------------------------
9/4/2007 18:17:25 - Process(4576.1) User(mqsvcprj1) Program(runmqchl.exe)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'PGMAPP1.T.PGMAPP2' ended abnormally.
ACTION:
Look at previous error messages for channel program 'PGMAPP1.T.PGMAPP2' in
the error files to determine the cause of the failure.
AMQ Error logs at the remote server :
04/09/2007 13:34:54 - Process(6328.1367) User(mqsvc002) Program(amqrmppa.exe)
AMQ9259: Connection timed out from host '162.148.117.12'.
EXPLANATION:
A connection from host '162.148.117.12' over TCP/IP timed out.
ACTION:
Check to see why data was not received in the expected time. Correct the
problem. Reconnect the channel, or wait for a retrying channel to reconnect
itself.
----- amqccita.c : 3340 -------------------------------------------------------
04/09/2007 13:34:54 - Process(6328.1367) User(mqsvc002) Program(amqrmppa.exe)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'PGMAPP1.T.PGMAPP2' ended abnormally.
ACTION:
Look at previous error messages for channel program 'PGMAPP1.T.PGMAPP2' in
the error files to determine the cause of the failure.
Has anyone faced similar issues ? Please advise for any possible reasons for the retrying . _________________ Regards,
MS |
|
Back to top |
|
 |
Vitor |
Posted: Tue Sep 04, 2007 5:12 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Are there any FDC or error messages at the target? Is the target box heavily loaded, possibly leading to the resource shortages mentioned in the message text?
When you say the "queue manager and other channels on the remote server are running fine" does this imply that this one does not? Have you tested the network link while the channel is in retry or just generally?
Also what platforms are the 2 queue managers on and what version(s) of MQ are they using? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Sep 04, 2007 5:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You really need to troubleshoot this from the other side (the receiver channel side).
It seems most likely that receiver side is running out of maxconns or system resources necessary to start another channel instance, when your channel starts up.
There could be a bunch of reasons for this, but you won't know what until you start looking at the errors on the other side. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
ms_mq |
Posted: Tue Sep 04, 2007 5:30 am Post subject: |
|
|
Acolyte
Joined: 23 Feb 2007 Posts: 69
|
Hi Vitor and Jeff,
Thanks for your replies.
I just forgot to mention .. Both are windows (Source is Win 2k and target is win 2003) . The MQ version on both servers are 6.0.2.
1. There are no FDCs generated at the target server .
2. The receiver channel is running on the target server
3.Yes, i tested the ping , tracert,telnet etc when the channel is retrying.
4. Not sure if this is a resource issue . Please advise how to check this .
5. But, the sender channel from the target server to my source is running fine and the
corresponding receiver channel is running fine.
I need to mention here is that both the queue managers are part of same cluster. Again the cluster sender channel to the target server was retrying and hence we decided to start P2P
channels between these servers , but ended up on the same issue.
Recycled the MQ service, rebooted the server .But nothing seems to be working.
Please advise. _________________ Regards,
MS |
|
Back to top |
|
 |
Vitor |
Posted: Tue Sep 04, 2007 5:37 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Are either of those supported platforms for v6.0.2?
Check resources using standard Windows tools. Ask your admin. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Sep 04, 2007 5:53 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
There may be errors logged on the receiver side that do not generate FDCs.
If there are FDCs generated on EITHER side, then these should be investigated first. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
ms_mq |
Posted: Tue Sep 04, 2007 6:31 am Post subject: |
|
|
Acolyte
Joined: 23 Feb 2007 Posts: 69
|
Hi,
I have defined sender channels to the same target server from another windows server and it is running fine without any issues. So can we conclude that the target server is ok and this problem iam facing might be due to some network issues ? But still the ping/tracert/telnet test is ok.
Please advise. _________________ Regards,
MS |
|
Back to top |
|
 |
Vitor |
Posted: Tue Sep 04, 2007 6:49 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
ms_mq wrote: |
So can we conclude that the target server is ok and this problem iam facing might be due to some network issues ? |
I'd say that was a bit premature.
Is the other windows server that works fine another Win2K box? With the same Windows patch level? I wonder about v6 on Win2K even though it is supported (I looked it up). I assuming you have it patched to SP4 as it appears to be working, though this could be the source of your issue.
Bottom line - sender & receiver channel are losing comms. If the network's working it's a software issue with the processes, probably resource related. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
ms_mq |
Posted: Wed Sep 05, 2007 1:21 am Post subject: |
|
|
Acolyte
Joined: 23 Feb 2007 Posts: 69
|
Hi ,
Sorry , what i tried was from a win 2003 server and it worked well.
You are right . The source win 2k server is running on SP 4. I checked the MQ6 manuals and it says win 2k does not support IPv6 .
But, the channels were working till this point . Not sure why this is not working now. Please let me know your suggestions. _________________ Regards,
MS |
|
Back to top |
|
 |
Nigelg |
Posted: Wed Sep 05, 2007 1:39 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
Find out what has changed since it was working, and change it back. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Sep 05, 2007 1:45 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
ms_mq wrote: |
But, the channels were working till this point . Not sure why this is not working now. Please let me know your suggestions. |
WinDoze has pulled it's usual trick of suddenly not working for no explainable reason?
My suggestion - move onto something more recent than Win2K, especially if you're trying to use IPv6. Something you'd not mentioned before. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
ms_mq |
Posted: Wed Sep 05, 2007 1:45 am Post subject: |
|
|
Acolyte
Joined: 23 Feb 2007 Posts: 69
|
The only change that has happened is that the remote server was applied service pack 2 . But, again the sender channel to another remote server which was applied SP 2 is working ok. It is really confusing. _________________ Regards,
MS |
|
Back to top |
|
 |
Vitor |
Posted: Wed Sep 05, 2007 1:47 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
ms_mq wrote: |
The only change that has happened is that the remote server was applied service pack 2 . But, again the sender channel to another remote server which was applied SP 2 is working ok. It is really confusing. |
And you seriously believe that both SP2 have applied identically? Does WinDoze ever do the same thing twice in response to identical stimulus?
It really sounds like you've got platform / network issues. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Sep 05, 2007 3:07 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Barring platform issues, have you checked the number of running channels (via channel status) on the target qmgr when the source goes into retry?
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed Sep 05, 2007 4:07 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
fjb_saper wrote: |
Barring platform issues, have you checked the number of running channels (via channel status) on the target qmgr when the source goes into retry?
Enjoy  |
...because you may be hitting Max Channels on that QM. But in that case there would be entries in the error log saying exactly that. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|