|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
persistent channel problem |
« View previous topic :: View next topic » |
Author |
Message
|
raj |
Posted: Mon Jul 22, 2002 5:17 am Post subject: persistent channel problem |
|
|
Centurion
Joined: 31 Mar 2002 Posts: 104
|
Hi ,
My channel proble is not cleared. I have installed MQSerie 5.1 on my home pc.I am getting the following error when trying the channel. When i ping the IP i am getting response.
_____________________________________________________________
AMQ9202: Remote host '(' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host '
(' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
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 TCP/IP is 10061 (X'274D'). 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 TCP/IP listening program, and try again.
________________________________________________________
Last edited by raj on Tue Jul 23, 2002 4:42 am; edited 1 time in total |
|
Back to top |
|
 |
mrlinux |
Posted: Mon Jul 22, 2002 6:11 am Post subject: |
|
|
 Grand Master
Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA
|
Did you set the listener to port 1411 or the default of 1414 ???? _________________ Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
Back to top |
|
 |
bduncan |
Posted: Mon Jul 22, 2002 7:16 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
|
You say that the ping works, but I'm assuming this is just a simple ping on the IP/port using the UNIX or MSDOS ping command. You should go into runmqsc and try the PING CHANNEL command. This will give you a more verbose answer and it is using the MQSeries channel mechanism rather than a simple TCP/IP ping. You might also want to try running the channel manually using the runmqchl command. It usually gives a more detailed description of the problem than the log files. _________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
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
|
|
|
|