| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Client Connection Problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| cecils |
 Posted: Tue Jun 11, 2002 2:11 am Post subject: MQ Client Connection Problem |
 |
|
Newbie
Joined: 11 Jun 2002
Posts: 7
|
Hi guys,
Hope you could help me out. I installed an mq server and client in two diff. machines that is connected to each other only since i am not connect to a local area network. i've manually defined the ip address of both machines with the same sub mask & gateway server. when i tried running the test program amqsputc in the client machine, i keep on getting an error in MQCONN with reason code 2059. I also get an error in the server machine. This is the error I got from the server machine:
-------------------------------------------------------------------------------
06/11/2002 18:05:48
AMQ9503: Channel negotiation failed.
EXPLANATION:
Channel '' between this machine and the remote machine could not be established
due to a negotiation failure.
ACTION:
Tell the systems administrator, who should attempt to identify the cause of the
channel failure using problem determination techniques. For example, look for
FFST files, and examine the error logs on the local and remote systems where
there may be messages explaining the cause of failure. More information may be
obtained by repeating the operation with tracing enabled.
-------------------------------------------------------------------------------
06/11/2002 18:05:48
AMQ9228: The TCP/IP responder program could not be started.
EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason
code was 0.
i have done everything that was said in the installation guide. what seems to be the problem. i hope you could help me out asap.
thanks,
cecil |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Tue Jun 11, 2002 7:10 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
From your description these machines are on there on network ????
if so then what are you using for a gateway ????? also can you ping each box ???
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| jlamond |
| Posted: Fri Jun 14, 2002 6:30 am Post subject: |
|
|
Voyager
Joined: 28 May 2002
Posts: 94
Location: Paris
|
Can you post the error message (if one) from the client machine MQSeries errors log as well as the error log (amqerrxx.log) from qmgrs/<you QM>/errors. Your answer is probably there.
Jean-Marc
_________________
Jean-Marc |
|
| Back to top |
|
|
| glen |
| Posted: Tue Jun 18, 2002 12:32 am Post subject: |
|
|
Novice
Joined: 05 Jun 2002
Posts: 13
Location: Dublin, Ireland.
|
If your machines are not connected to a network, what are you using as a gateway? a router, switch, or one of the machines in your test environment?
are you sure you are using valid IP addresses?
have you set the MQSERVER variable with the correct port?
if you echo %mqserver%, correctly configured should return
S_(servername)/TCP/(ip_addr as ***.***.***.***)(port)
eg. S_dev/TCP/10.10.10.1(1415)
note this is case sensitive |
|
| Back to top |
|
|
| xchen |
| Posted: Thu Dec 11, 2003 5:34 pm Post subject: Try to alter CCSID for qmgr |
|
|
Newbie
Joined: 11 Dec 2003
Posts: 2
|
Hi Cecils,
Try to change your qmgr CCSID from 923 to 819, then restart the qmgr. I guess it might fixt the problem. Good luck 
Regards,
Xin |
|
| 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
|
|
|
|
