| Author |
Message
|
| jumipe |
 Posted: Thu Feb 11, 2010 12:57 am Post subject: AMQ9202: Remote host '' not available, retry later |
 |
|
Newbie
Joined: 11 Feb 2010
Posts: 4
|
Hello!
I am using MQ 6.0.1.2 on OVMS 8.3.1.
I am having this message on AMQERR*.LOG
AMQ9202: Remote host '' not available, retry later
I think this is becaus one of clients have lost connection.
Now i would which client is having problem. Host '' does not tell much.
Can someboy help me? |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Feb 11, 2010 2:06 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Too little information to provide targeted help...
Obvious questions:
1. a) Server-to-Server, or b) Client?
2. If a), what channel(s) is showing as in retry etc. and have you checked the infrastructure stated in the CONNAME?
No doubt other questions will arise from your answers...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| jumipe |
| Posted: Thu Feb 11, 2010 2:49 am Post subject: |
|
|
Newbie
Joined: 11 Feb 2010
Posts: 4
|
Here comes more information:
Client connects to server using MQCONNX to channel like this:
DEFINE CHANNEL(CH.SVR.***) +
CHLTYPE(SVRCONN) +
TRPTYPE(TCP)
This is full error message:
----- BROOT:[LIB.COMMS.UNIX]AMQCRHNA.C;1 : 813 --------------------------------
02/11/10 10:44:58 - Process(1159.175) User(MQS_SERVER) Program(AMQRMPPA.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 65535
(X'FFFF'). 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. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Feb 11, 2010 2:59 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
1. Can you ping the remote host from the server hosting your client?
2. Is the Listener running for the queue manager on the remote host?
3. Have firewall changes been made recently?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| jumipe |
| Posted: Thu Feb 11, 2010 3:09 am Post subject: |
|
|
Newbie
Joined: 11 Feb 2010
Posts: 4
|
1.I can ping clients using IP-address
2.Remote host is client (no queue manager ) 
3.We have just imported old server environment to new hardware, OS versio and MQ version.
I think error messages are caused because some of client programs are in moving machine connected via WLAN
Main question is: How can i know which one of clients is host ''? At moment i am having about 30 client connections. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Feb 11, 2010 3:18 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Communication is either Server-to-Server, or Client-to-Server; a queue manager hosting a SVRCONN does not initiate connection to a client, the queue manager is the passive party. Time to get your head into the Intercommunications manual methinks.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| jumipe |
| Posted: Thu Feb 11, 2010 3:37 am Post subject: |
|
|
Newbie
Joined: 11 Feb 2010
Posts: 4
|
|
| Back to top |
|
|
| exerk |
| Posted: Thu Feb 11, 2010 3:53 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
If this:
| Quote: |
----- BROOT:[LIB.COMMS.UNIX]AMQCRHNA.C;1 : 813 --------------------------------
02/11/10 10:44:58 - Process(1159.175) User(MQS_SERVER) Program(AMQRMPPA.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 65535
(X'FFFF'). 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. |
Is from the queue manager log (the queue manager that hosts the SVRCONN) it suggests to me that either:
1. The inbound client is trying to establish a connection but the queue manager is unable to route back to the server hosting the client, or;
2. You are trying to initiate a connection from the queue manager to the client (unlikely you are doing this, but I've seen it tried).
Check with your network/firewall people that if 'packets in' are getting through to the queue manager, that 'packets out' are getting to the server hosting the client. just because an ICMP ping works does not mean that packet filtering is not dropping the outbound traffic from the server hosting the queue manager; I suspect that in your case host is describing the server with the client on it.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 11, 2010 8:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jumipe wrote: |
1.I can ping clients using IP-address
2.Remote host is client (no queue manager )
3.We have just imported old server environment to new hardware, OS versio and MQ version.
I think error messages are caused because some of client programs are in moving machine connected via WLAN
Main question is: How can i know which one of clients is host ''? At moment i am having about 30 client connections. |
As you moved to a new hardware, possibly on a different tcp/ip segment, make sure that the tcp/ip path back to all clients is possible.
Checking network setup, routing and firewall rules seems the way to go...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
