| Author | Message | 
		
		  | xtuyaowu | 
			  
				|  Posted: Tue Feb 06, 2007 12:22 am    Post subject: AMQ9213: A communications error for TCP/IP occurred. |   |  | 
		
		  | Newbie
 
 
 Joined: 01 Feb 2007Posts: 4
 
 
 | 
			  
				| hi everyone i got the errors when tried to send message between too computers : 
 remote(SERVER):
 manager:QM_SENDER
 remote queue:QR
 transQueue:QX
 channel:    C
 QM_SENDER
 ------------------------
 DEFINE      QREMOTE     (QR)
 RNAME         (QL)
 RQMNAME    (QX)
 REPLACE
 DEFINE      QLOCAL       (QX)
 USAGE        (XMITQ)
 REPLACE
 DEFINE      CHANNEL    (C)
 CHLTYPE    (SDR)
 TRPTYPE    (TCP)
 CONNAME    ('192.168.1.80(1416)')
 XMITQ      (QX)
 REPLACE
 
 
 
 local(TAN):
 manager:  QM_RECEIVER
 localqueue:QL
 channel:    C
 QM_RECEIVER
 ------------------------------------------------
 DEFINE      QLOCAL     (QL)
 REPLACE
 DEFINE      CHANNEL   (C)
 CHLTYPE    (RCVR)
 TRPTYPE    (TCP)
 REPLACE
 
 runmqlsr -m QM_RECEIVER -t tcp -p 1416&
 
 runmqsc       QM_SENDER
 start  channel(C)
 
 errors:
 4 : PING CHANNEL(C)
 AMQ9213: A communications error for TCP/IP occurred.
 
 log:
 ----- amqrccca.c : 777 --------------------------------------------------------
 02/06/2007 10:59:55 AM - Process(6282.1) User(mqm) Program(runmqchl)
 AMQ9002: Channel 'C' is starting.
 
 EXPLANATION:
 Channel 'C' is starting.
 ACTION:
 None.
 -------------------------------------------------------------------------------
 02/06/2007 10:59:55 AM - Process(6282.1) User(mqm) Program(runmqchl)
 AMQ9213: A communications error for TCP/IP occurred.
 
 EXPLANATION:
 An unexpected error occurred in communications.
 ACTION:
 The return code from the TCP/IP (connect) call was 113 (X'71'). Record these
 values and tell the systems administrator.
 ----- amqccita.c : 1120 -------------------------------------------------------
 02/06/2007 10:59:55 AM - Process(6282.1) User(mqm) Program(runmqchl)
 AMQ9999: Channel program ended abnormally.
 
 EXPLANATION:
 Channel program 'C' ended abnormally.
 ACTION:
 Look at previous error messages for channel program 'C' in the error files to
 determine the cause of the failure.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Anirud | 
			  
				|  Posted: Tue Feb 06, 2007 12:49 am    Post subject: |   |  | 
		
		  |  Master
 
 
 Joined: 12 Feb 2004Posts: 285
 Location: Vermont
 
 | 
			  
				| Check to see if the listener is running. 
 Also, the QRemote QR on QM_SENDER is not right.   It should be
 
 
   
	| Code: |  
	| DEFINE QREMOTE(QR) RNAME(QL) RQMNAME(QM_RECEIVE) XMITQ(QX) REPLACE 
 |  
 HTH.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | xtuyaowu | 
			  
				|  Posted: Tue Feb 06, 2007 1:07 am    Post subject: |   |  | 
		
		  | Newbie
 
 
 Joined: 01 Feb 2007Posts: 4
 
 
 | 
			  
				| hi by shutdown firework  it is can ping but still could not get messages: 
 [mqm@192 bin]$ ./amqsput QR   QM_SENDER
 Sample AMQSPUT0 start
 target queue is QR
 haha
 
 Sample AMQSPUT0 end
 
 
 bash-3.1$ ./amqsget QL QM_RECEIVER
 Sample AMQSGET0 start
 no more messages
 Sample AMQSGET0 end
 
 why??
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Vitor | 
			  
				|  Posted: Tue Feb 06, 2007 1:17 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| 
 How long have you got?
   
 Is there no dlq on the receiver causing a failing message to be deleted? Do you have a channel initiator set up and is it working? Have you looked at the channel count to see if the message actually left the sender? Have you checked the xmitq to see if the message is stuck there? Have you checked the dlq on the receiving box? ? Have you checked the logs? Have you checked the manuals? Have you tried any diagnostics already or just posted?
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Anirud | 
			  
				|  Posted: Tue Feb 06, 2007 1:38 am    Post subject: |   |  | 
		
		  |  Master
 
 
 Joined: 12 Feb 2004Posts: 285
 Location: Vermont
 
 | 
			  
				| From the configuration that you have posted... The destination Queue Manager in the message header will be QX, but the actual destination queue manager is QM_RECEIVE.  So, when the messages gets to QM_RECEIVE, MQ will not be able to resolve the queue manager name (assuming you don't have a queue manager alias configured on the receiving queue  manager).   If the message is non-presistent, then it will be lost.  If the message is a presistent message, it will not be lost and can be found on any one of what Vitor is asking you to check.
 
 That was the reason I asked you to correct the QR definition.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |