| Author |
Message
|
| themvv |
 Posted: Wed Nov 23, 2005 2:04 am Post subject: give all |
 |
|
Novice
Joined: 22 Jul 2003
Posts: 15
|
I have meet this error
Please give our solusion in public , don't PM
--- amqccita.c : 973 --------------------------------------------------------
11/15/2005 15:28:36
AMQ9201: Allocate failed to host '10.3.64.56'.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 10.3.64.56 was not
successful.
ACTION:
The error may be due to an incorrect entry in the TCP/IP parameters contained
in the channel definition to host 10.3.64.56. Correct the error and try again.
If the error persists, record the error values and contact your systems
administrator. The return code from the TCP/IP (connect) call was 10065
(X'2751'). It may be possible that the listening program at host 10.3.64.56 is
not running. If this is the case, perform the relevant operations to start the
listening program for protocol TCP/IP and try again.
----- amqccita.c : 958 --------------------------------------------------------
11/17/2005 11:54:28
AMQ9206: Error sending data to host Webtincc (10.3.64.56).
EXPLANATION:
An error occurred sending data over TCP/IP to Webtincc (10.3.64.56). This may
be due to a communications failure.
ACTION:
The return code from the TCP/IP(send) call was 10054 X('2746'). Record these
values and tell your systems administrator.
----- amqccita.c : 2052 ------------------------------------------------------- |
|
| Back to top |
|
 |
| Tibor |
| Posted: Wed Nov 23, 2005 2:40 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
These are network problems:
| Quote: |
WSAEHOSTUNREACH (10065): No route to host. A socket operation was attempted to an unreachable machine.
WSAECONNRESET (10054): Connection reset by peer. An existing connection was forcibly closed by the remote peer. This normally results if the peer application on the remote machine is suddenly stopped, the machine is rebooted, or the peer application used a "hard close" on the remote socket. This error may also result if a connection was broken due to "keep-alive" activity detecting a failure while one or more operations are in progress. Operations in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. |
HTH,
Tibor |
|
| Back to top |
|
|
| themvv |
| Posted: Wed Nov 23, 2005 6:09 pm Post subject: |
|
|
Novice
Joined: 22 Jul 2003
Posts: 15
|
Someone also said that is network problem, but i still copy file an connect to server.
If MQ is well than FTP (or Copy file), while copy file well but MQ not work?? |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Wed Nov 23, 2005 7:46 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
But FTP uses a different port right?
Do you have the MQ port setup properly in TCPIP? |
|
| Back to top |
|
|
| themvv |
| Posted: Wed Nov 23, 2005 8:02 pm Post subject: |
|
|
Novice
Joined: 22 Jul 2003
Posts: 15
|
My MQ port using 1515, V5.3 CS07
I think MQ port is not problem because My System is:
I has a MQ Server. They connect to other MQ server well and connected by some MQ client. One MQ client in local machine connect well, but other in network don't connect and have err log:
----- amqccita.c : 973 --------------------------------------------------------
11/15/2005 15:28:36
AMQ9201: Allocate failed to host '10.3.64.56'.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 10.3.64.56 was not
successful.
ACTION:
The error may be due to an incorrect entry in the TCP/IP parameters contained
in the channel definition to host 10.3.64.56. Correct the error and try again.
If the error persists, record the error values and contact your systems
administrator. The return code from the TCP/IP (connect) call was 10065
(X'2751'). It may be possible that the listening program at host 10.3.64.56 is
not running. If this is the case, perform the relevant operations to start the
listening program for protocol TCP/IP and try again.
----- amqccita.c : 958 --------------------------------------------------------
11/17/2005 11:54:28
AMQ9206: Error sending data to host Webtincc (10.3.64.56).
EXPLANATION:
An error occurred sending data over TCP/IP to Webtincc (10.3.64.56). This may
be due to a communications failure.
ACTION:
The return code from the TCP/IP(send) call was 10054 X('2746'). Record these
values and tell your systems administrator.
----- amqccita.c : 2052 ------------------------------------------------------- |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Wed Nov 23, 2005 8:28 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Care to post your channel definitions? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Nov 25, 2005 6:00 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you sure the firewall is open for the port you are trying to access ?
 |
|
| Back to top |
|
|
| themvv |
| Posted: Mon Nov 28, 2005 11:59 pm Post subject: |
|
|
Novice
Joined: 22 Jul 2003
Posts: 15
|
| I use telnet for testing firewall . it OK (not firewall my port) |
|
| Back to top |
|
|
| gunter |
| Posted: Tue Nov 29, 2005 12:46 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
I assume both systems are windows 2000 server.
Did you check the event-logs on both systems?
And check the the network between both systems in both directions. I'm not sure, but I have in mind, I had a problem to start a channel from system a to b because there was no route between b and a.
I believe the problem is the network to your target system or the targetsystem itself. If the queuemanager on the sender side has connections to other systems, I don't think you can find the problen here.
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
|
|
