| Author |
Message
|
| tapak |
 Posted: Wed Feb 15, 2006 7:42 am Post subject: Getting 2059 while using amqsputc on a remote machine |
 |
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
I got a 2059 error while using amqsputc from a remote machine . I created the server connection channel in the QManager and set the MQSERVER variable in the remote machinebefore running amqsputc .
WHen I run amqsputc from the same machine as qmanager it works . Any thoughts ?
_________________
IBM Certified Solution Designer -- WebSphere MQ V5.3
IBM Certified Solution Designer -- WebSphere Business Integration - Message Broker V5
IBM Certified Specialist -- IBM WebSphere App Svr Advd Single Svr Ed. for Multiplatforms (Java) |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Feb 15, 2006 7:50 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
could there be a firewall blocking the port MQ is listening on between the two machines (default: 1414)?
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 15, 2006 7:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Does amqscnx work?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| tapak |
| Posted: Wed Feb 15, 2006 8:02 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
I dont have a exe with name amqxcnx. I am checking with sys admin if there is a firewall issue. Guess it may be a firewall issue . Here is the error I am getting in mqerror log in the client machine.
2/15/2006 10:53:59
AMQ9202: Remote host 'hostname (ipaddress) (1415)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'hostname
(ipaddress) (1415)' 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
10060 (X'274C'). 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.
_________________
IBM Certified Solution Designer -- WebSphere MQ V5.3
IBM Certified Solution Designer -- WebSphere Business Integration - Message Broker V5
IBM Certified Specialist -- IBM WebSphere App Svr Advd Single Svr Ed. for Multiplatforms (Java) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 15, 2006 8:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Sorry, it's amqscnxc, not amqscnx. It should be in with amqsputc.
It could also be that the listener is not using port 1415.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Feb 15, 2006 8:09 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| tapak wrote: |
| AMQ9202: Remote host 'hostname (ipaddress) (1415)' not available |
This is the key. Example correct CONNAMEs are
127.0.0.1(1415)
mymachine.mycompany.com(1415)
12.34.56.78(1415) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 15, 2006 8:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mvic wrote: |
| tapak wrote: |
| AMQ9202: Remote host 'hostname (ipaddress) (1415)' not available |
This is the key. |
Unless tapak changed that manually when posting.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Feb 15, 2006 8:14 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Well... anything is possible, but tapak did say:
| Quote: |
WHen I run amqsputc from the same machine as qmanager it works . Any thoughts ?
|
so I assume that he's got the server and MQSERVER set correctly...
_________________
-wayne |
|
| Back to top |
|
|
| tapak |
| Posted: Wed Feb 15, 2006 8:34 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
Jeff is correct . I removed the ipaddress while posting . Here is the error I cot when I used the AMQSCNX. I got the same error listed earlier in the mqerror log.
Sample AMQSCNXC start
Connecting to the default queue manager
with no client connection information specified.
MQCONNX ended with reason code 2059
_________________
IBM Certified Solution Designer -- WebSphere MQ V5.3
IBM Certified Solution Designer -- WebSphere Business Integration - Message Broker V5
IBM Certified Specialist -- IBM WebSphere App Svr Advd Single Svr Ed. for Multiplatforms (Java) |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Feb 15, 2006 8:38 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
so the cheap hack is to try to telnet to that port, if it gets rejected straight away, then either (1) mq isn't listening on that port or (2) a firewall is blocking that port... if telnet sorta hangs for a spell, then you're getting through (and likely to see an error in amqerr01.log on the server);
telnet ipaddress 1415
_________________
-wayne |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Feb 15, 2006 8:46 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| tapak wrote: |
| Jeff is correct . I removed the ipaddress while posting . |
It helps if you mention this kind of thing when altering what would otherwise appear to be verbatim copy/paste error reports.
Anyway, I looked up Win32 error code 10060 and it says "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."
So, we are probably looking at a basic connectivity issue here. Others have mentioned the possibility of a firewall preventing connections. Did you find an answer for this?
As Wayne points out, the test using telnet will help establish independently whether or not there is IP connectivity between local and remote machines. It seems likely there isn't connectivity.
EDIT: alter 3rd paragraph |
|
| Back to top |
|
|
| tapak |
| Posted: Wed Feb 15, 2006 10:58 am Post subject: windowsxp firewall was enabled. |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
Windows XP firewall was enabled in the server machine . Disabling the firewall solved the issue . Thank you all for your inputs.
_________________
IBM Certified Solution Designer -- WebSphere MQ V5.3
IBM Certified Solution Designer -- WebSphere Business Integration - Message Broker V5
IBM Certified Specialist -- IBM WebSphere App Svr Advd Single Svr Ed. for Multiplatforms (Java) |
|
| Back to top |
|
|
|
|
