| Author |
Message
|
| nosnhoj |
 Posted: Wed Jan 18, 2006 12:43 pm Post subject: Connectivity problem |
 |
|
Apprentice
Joined: 07 Sep 2005
Posts: 40
Location: Markham On.
|
I have an HPUX qmgr, and a remote WIN2000 queue manager. I am able to connect to both qmgrs via MQJexplorer - however
When I try and start a sender channel from either side (HPUX or WINDOWS) they just stay 'initializing'. From the Windows qmgr I am able to ping my HPUX channel successfully, but from my hpux, the ping channel returns Remote host 'web18 (xxx.xxx.xx.xxx) (1441)' not available, retry later.
And both sides are still "Initializing...."
I am not able to see the error log on the Windows box (yet), and the HP box just shows AMQ9202 "The return code from TCP/IP is 238 (X'EE')."
I know the listeners are OK becuase MQJexplorer is connected to both.
I've exhasuted myself searching the boards, and am hoping your experience might have an answer for me - or a kick in the right direction
Thx |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Wed Jan 18, 2006 2:24 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Is the listener running on the correct port on the Windows Server?
Here's what the WMQ Messges Guide has to day about AMQ9202:
| Quote: |
AMQ9202 Remote host ’&3’ not available, retry
later.
Explanation: The attempt to allocate a conversation
using &4 to host ’&3’ was not successful. However the
error may be a transitory one and it may be possible to
successfully allocate a &4 conversation later.
User Response: Try the connection again later. If the
failure persists, record the error values and contact |
This is one of the reason why the Hitchhikers Guide to the Galaxy is more popular though it does contain many innacuracies and much that is hipocriful.
I don't have a list of HPUX TCP/IP Return Codes but I'm sure if you spend a little time on Google you'll be able to track one down.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Last edited by csmith28 on Wed Jan 18, 2006 4:20 pm; edited 1 time in total |
|
| Back to top |
|
|
| JT |
| Posted: Wed Jan 18, 2006 2:53 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| but from my hpux, the ping channel returns Remote host 'web18 (xxx.xxx.xx.xxx) (1441)' not available, retry later |
Sometimes we gloss over things quickly and miss the obvious, so are you sure the port is 1441, and not the default 1414 ? |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Jan 18, 2006 4:17 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Yeah, that's why I asked.
| Quote: |
| Is the listener running on the correct port on the Windows Server? |
I am fairly certain the listener process on the would fail to start on the Windows Server if something were already bound to port 1441 or 1414 and I was giving the poster the benifit of the doubt.
AMQ9202 indicates that the SDR Channel MCA could not estabish a connection to the RCVR MCA let alone start a negotiation.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jan 18, 2006 9:50 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I have seen some weird behavior with the listeners in V6 using the Eclipse GUI on an XP platform...
A) The listener would not work whatever we tried. On start it would look like it is starting and die soon after.
B) Magic it worked.
A) created and started the listener. A sender channel to the qmgr started before the listener ever got to running status.
B) Deleted and recreated the listener. Set the tcp bakup # to 100. Had any sdr channel stopped. Waited for listener to hit running status. Started the sdr channel... It worked !!
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nosnhoj |
| Posted: Thu Jan 19, 2006 5:43 am Post subject: |
|
|
Apprentice
Joined: 07 Sep 2005
Posts: 40
Location: Markham On.
|
| Somebode 'suddenly' remembered that there may be a 'firewall' issue.... thanks for the responses, I'll update when I find out if that fixed it |
|
| Back to top |
|
|
| nosnhoj |
| Posted: Mon Jan 23, 2006 6:51 am Post subject: |
|
|
Apprentice
Joined: 07 Sep 2005
Posts: 40
Location: Markham On.
|
| And sure enough, there was a firewall, but only blocking outgoing connections from the HPUX server. |
|
| Back to top |
|
|
|
|
