| Author |
Message
|
| graigue61 |
 Posted: Tue Jan 30, 2007 1:33 am Post subject: CHANNEL IN RETRY AFTER UPGRADE |
 |
|
Newbie
Joined: 07 Nov 2006
Posts: 9
Location: Ireland
|
Hi,
we recently updated our windows server from MQ 5.3 to MQ 6. All of our channels are connecting from windows to iseries servers(MQ 5.3) and all are working except for one. I have tried resetting,resolving etc.. on both sides (windows & iseries) but nothing solves the problem. Is this a problem with MQ 6 connecting to MQ 5.3 ? I've included the error below from the log:
30/01/2007 07:53:16 - Process(5532.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
AMQ9202: Remote host '' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using to host '' was not successful.
However the error may be a transitory one and it may be possible to
successfully allocate a conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from is 9
(X'9'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host ''
was not running. If this is the case, perform the relevant operations to start
the listening program, and try again.
Any ideas ?
thx
_________________
Lisa |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Tue Jan 30, 2007 2:22 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
why did you reset the channel? was there a sequence number problem?
why did you resolve the channel? was the channel indoubt?
in case of an error, you should first try to find out the cause of the error. just trying commands without knowing what the error is and whether the command may help is a good chance to make things worse.
do you use the lates fixpac of version 6?
how does the channel looks like? are you sure you do not haqve a networking problem as described?
do you see anything in the remote queuemanager log?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 30, 2007 2:35 am Post subject: Re: CHANNEL IN RETRY AFTER UPGRADE |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| graigue61 wrote: |
AMQ9202: Remote host '' not available, retry later.
|
This sounds more like network than MQ - I am especially interested by the blank host name it's trying to find. What host name is the channel set to look for?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| graigue61 |
| Posted: Tue Jan 30, 2007 3:54 am Post subject: |
|
|
Newbie
Joined: 07 Nov 2006
Posts: 9
Location: Ireland
|
the fixpack used is 6.0.2.0
the channel is set to connect by ip address. I have talked with the network team and they have said that there is no problem with access across the network ( I can also ping the iseries server and telnet to the port MQ port).
The reason that I reset the channels was due to the fact that all the other channels were running without problem, so to me, it looked like messages may have been knocked out of synce by the upgrade.
The only thing in the remote queue manager log was a message saying that the tcp responder service could not be started. There may be jobs waiting or the subsystem may need to be restarted. I did restart the subsystem on the iseries server.
Also, we have an old server with MQ version 5.3 which can connect without problems. This old server is side by side with the new one, so it doesn't look like a network issue to me.
Thx
_________________
Lisa |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Tue Jan 30, 2007 4:56 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
things i would try (but only if you are sure this is not a networking problem):
search at ibm supprot if there are known issues
define a new channel on the same mqseries to the same IP address and try if that one is able to connect (to exclude the "old" channel is in error because of a bad object migration)
another try:
create a new MQ version 6 queuemanager on that machine, define the same channel and try again (now this can not be caused by migration)
if it still does not work i still suspect a networking issue.....
_________________
Regards, Butcher |
|
| Back to top |
|
|
| graigue61 |
| Posted: Wed Jan 31, 2007 2:06 am Post subject: |
|
|
Newbie
Joined: 07 Nov 2006
Posts: 9
Location: Ireland
|
just an update:
I phoned IBM and apparently this is a known issue with fixpack 6.0.2.0 and 6.0.1.1
They are sending me a fix, so I'll let you know if it works when I get it
_________________
Lisa |
|
| Back to top |
|
|
| graigue61 |
| Posted: Wed Jan 31, 2007 4:09 am Post subject: |
|
|
Newbie
Joined: 07 Nov 2006
Posts: 9
Location: Ireland
|
HI, as a follow up to this, the fix that I was given works. It replaces the files bin\amqcctca.dll and bin\amqcltca.dll . The problem summary is :On Windows, WebSphere MQ uses a platform-specific function to
convert numeric IP address bytes into their string
representation. This is used for display purposes in channel
status entries and error logs.
The Windows implementation of this function contained an
incorrect validation check on the IP address which caused it
to reject certain IP addresses.
In the fix, the validation code is removed.
Thanks for everyone help
_________________
Lisa |
|
| Back to top |
|
|
| vpsingh |
| Posted: Mon Mar 05, 2007 8:51 am Post subject: Windows implementation of Websphere MQ Client issue |
|
|
Newbie
Joined: 05 Mar 2007
Posts: 2
Location: Chicago, IL, USA
|
Hi; thanks for posting the reply - I am facing a similar situation and am wondering if its possible for you to send me the the fix that IBM sent you. I tried to get IBM support but since I am using only the MQ Client, I don't have software support with them at all and they refuse to provide support without buying the MQ Server!
Any help would be greatly appreciated.
Thanks! |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 05, 2007 8:53 am Post subject: Re: Windows implementation of Websphere MQ Client issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vpsingh wrote: |
| I am using only the MQ Client |
I didn't think the fixpacks applied to the clients, only to the server side code....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vpsingh |
| Posted: Mon Mar 05, 2007 10:04 am Post subject: Windows implementation of Websphere MQ Client issue |
|
|
Newbie
Joined: 05 Mar 2007
Posts: 2
Location: Chicago, IL, USA
|
Okay; I'm new at WebSphere so don't know exactly what should apply where. However, when trying amqsputc.exe, and specifying the queue and queue manager name as provided for the server I am trying to connect to and putting the channel file in the correct place and specifying the environment variables, I still get the error:
-----------------------------------------------------------------------------
Remote host '' not available, retry later.
The attempt to allocate a conversation using to host '' was not successful. However the error may be a transitory one and it may be possible to successfully allocate a conversation later.
------------------------------------------------------------------------------ |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 06, 2007 12:33 am Post subject: Re: Windows implementation of Websphere MQ Client issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vpsingh wrote: |
| ...as provided for the server I am trying to connect to |
So you're not just using a client, and you should get whoever administers the queue manager you're trying to connect to to contact IBM Support, obtain the fixpacks quoted in this post as per their license agreement, apply them and solve your problem!
QED 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| EKhalil |
| Posted: Wed Mar 07, 2007 5:28 am Post subject: CHANNEL ENDING ABNORMALLY |
|
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
MQ version 6.0 (win platform) with the latest fix pack 6.0.2.0 including amqcctca.dll and AAAamqcltca.dll fix connecting to 5.3 z/os qmgr
After upgrade to v 6.0, the channel below is experiencing difficulties in 5 minute cycles. The connection is established, channel runs, however every 5 minutes host becomes unavailable, TCP connection is dropped and channel ends abnormally then the channel is automatically restarted. This results in quite a few expired messages...Anyone with similar issues ??? Anyone with suggestions ???
3/7/2007 08:12:07 - Process(8184.1) User(EVAK) Program(runmqchl.exe)
AMQ9202: Remote host '' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using to host '' was not successful.
However the error may be a transitory one and it may be possible to
successfully allocate a conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from is 9
(X'9'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host ''
was not running. If this is the case, perform the relevant operations to start
the listening program, and try again.
----- amqcrhna.c : 390 --------------------------------------------------------
3/7/2007 08:12:07 - Process(8184.1) User(EVAK) Program(runmqchl.exe)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'QA01.VQEQ' ended abnormally.
ACTION:
Look at previous error messages for channel program 'QA01.VQEQ' in the
error files to determine the cause of the failure.
----- amqrccca.c : 777 -------------------------------------------------------- |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 07, 2007 5:31 am Post subject: Re: CHANNEL ENDING ABNORMALLY |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| EKhalil wrote: |
| After upgrade to v 6.0, the channel below is experiencing difficulties in 5 minute cycles. The connection is established, channel runs, however every 5 minutes host becomes unavailable, TCP connection is dropped and channel ends abnormally then the channel is automatically restarted. |
Any chance there's a firewall (or similar network hardware) either deciding the connection's inactive and dropping it, or attempting to switch / load balance / redistribute / etc the connection causing the channel to fail?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| EKhalil |
| Posted: Wed Mar 07, 2007 6:07 am Post subject: |
|
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
TY for your suggestion...Well, the only thing that has changed in this environment is MQ version, all others remaining constant. Things were running smooth and this channel did not exibit any problems untill the upgrade of MQ. I do not believe that it has anything to do with load balancing or firewall due to what I've mentioned above but you never know... I am putting a trace on that port to hopefully pin point what's doing this...Meanwhile please feel free to provide any input as we are very eager to get this resolved,
Eva |
|
| Back to top |
|
|
| EKhalil |
| Posted: Thu Mar 08, 2007 6:34 am Post subject: |
|
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
| The trace revealed that processes running channels were dying at 5 min intervals then coming back up with new process id's on new port numbers. IMB has sent me the newest fix for this. It's the same 2 dlls used in previous fix but with February updates. |
|
| Back to top |
|
|
|
|
