| Author | 
		  Message
		 | 
		
		  | raz | 
		  
		    
			  
				 Posted: Wed Jun 18, 2008 7:18 am    Post subject: MQ TCP/IP errors | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 10 Jul 2007 Posts: 70
  
  | 
		  
		    
			  
				I'm using MQ6.0.2.1 on Solaris10 and getting the following errors in my MQ error very frequently
 
 
 
Program(amqrmppa.exe)
 
AMQ9208: Error on receive from host 102 (102.10.0.2).
 
 
EXPLANATION:
 
An error occurred receiving data from 102 (102.10.0.2) over TCP/IP. This may be due to a communications failure.
 
ACTION:
 
The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these values and tell the systems administrator.
 
----- amqccita.c : 3073
 
-------------------------------------------------------
 
6/10/2008 11:29:00 - Process(5048.14621) User(MUSR_MQADMIN)
 
Program(amqrmppa.exe)
 
AMQ9492: The TCP/IP responder program encountered an error.
 
 
EXPLANATION:
 
The responder program was started but detected an error.
 
ACTION:
 
Look at previous error messages in the error files to determine the error encountered by the responder program.
 
----- amqrmrsa.c : 459 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | poker | 
		  
		    
			  
				 Posted: Wed Jun 18, 2008 11:51 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 14 Mar 2006 Posts: 20
  
  | 
		  
		    
			  
				This shows error on ur Network. 
 
Would u try pinging the IP address from the machine. Also there is a fixpac , pls check if it is for Solaris. There was TCP/IP issue. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | raz | 
		  
		    
			  
				 Posted: Wed Jun 18, 2008 11:54 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 10 Jul 2007 Posts: 70
  
  | 
		  
		    
			  
				| I'm using MQ 6.0.2.1, could you tell me the fixpack version. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Gaya3 | 
		  
		    
			  
				 Posted: Wed Jun 18, 2008 10:32 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi
 
 Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US 
  | 
		  
		    
			  
				go for 6.0.2.3.
 
 
plz verify why the network is going down in some intervals of time.
 
 
do telnet <ipaddress> <port no> _________________ Regards
 
Gayathri
 
-----------------------------------------------
 
Do Something Before you Die | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | gbaddeley | 
		  
		    
			  
				 Posted: Wed Jun 18, 2008 11:39 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Knight
 
 Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia 
  | 
		  
		    
			  
				
   
	| Quote: | 
   
  
	Program(amqrmppa.exe)
 
AMQ9208: Error on receive from host 102 (102.10.0.2).
 
 
EXPLANATION:
 
An error occurred receiving data from 102 (102.10.0.2) over TCP/IP. This may be due to a communications failure.
 
ACTION:
 
The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these values and tell the systems administrator.
 
----- amqccita.c : 3073
 
-------------------------------------------------------
 
6/10/2008 11:29:00 - Process(5048.14621) User(MUSR_MQADMIN)  | 
   
 
 
 
Solaris?  That looks like windows to me.
 
 
1054 is a Windows Sockets error, "connection reset by peer".  ie. the other end of the channel dropped the session. _________________ Glenn | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | blovell | 
		  
		    
			  
				 Posted: Thu Jul 10, 2008 9:41 am    Post subject: Possible Sequence Break | 
				     | 
			   
			 
		   | 
		
		
		    Acolyte
 
 Joined: 08 Feb 2006 Posts: 63 Location: Alpharetta, GA 
  | 
		  
		    
			  
				I encountered the same issue on a SVR channel to one of my clients.  I looked at the network.  I ran numerous SNOOP traces and had my network engineering through some monitoring tools on the router.  What I found was my client side was erroring for sequence errors.  After doing a channel reset at both ends the issue cleared. _________________ Bradley M. Lovell | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |