|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| TCP/IP read() call was 104 (X'68') | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | jim | 
			  
				|  Posted: Wed Nov 27, 2013 5:45 pm    Post subject: TCP/IP read() call was 104 (X'68') |   |  |  
		  | Voyager
 
 
 Joined: 26 Nov 2013Posts: 94
 
 
 | 
			  
				| Hello All, 
 When application is tring to connect QMGR getting MQRC 2009 using SVRCONN channel
 
 Please find the error log
 
 AMQ9208: Error on receive from host 10.X.Y.Z (10.X.Y.Z).
 
 EXPLANATION:
 An error occurred receiving data from 10.X.Y.Z (10.X.Y.Z) over
 TCP/IP. This may be due to a communications failure.
 ACTION:
 The return code from the TCP/IP read() call was 104 (X'68'). Record these
 values and tell the systems administrator.
 
 In addition, we would see the following errors on the MQ "server" logs:
 
 AMQ9206: Error sending data to host 10.a.b.c
 (10.a.b.c)(port#).
 
 EXPLANATION:
 An error occurred sending data over TCP/IP to 10.a.b.c
 (10.a.b.c)(port#). This may be due to a communications failure.
 ACTION:
 The return code from the TCP/IP(write) call was 104 X('68'). Record these
 values and tell your systems administrator.
 
 The application getting frequently getting  MQRC 2009 But after some time the App is able to connect.
 
 Kindly suggest on it.
 
  |  |  
		  | Back to top |  |  
		  |  |  
		  | smdavies99 | 
			  
				|  Posted: Wed Nov 27, 2013 11:16 pm    Post subject: |   |  |  
		  |  Jedi Council
 
 
 Joined: 10 Feb 2003Posts: 6076
 Location: Somewhere over the Rainbow this side of Never-never land.
 
 | 
			  
				| 
   
	| Quote: |  
	| This may be due to a communications failure.
 
 |  
 IMHO, the most frequent cause of 2009 errors are network glitches.
 _________________
 WMQ User since 1999
 MQSI/WBI/WMB/'Thingy' User since 2002
 Linux user since 1995
 
 Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | PaulClarke | 
			  
				|  Posted: Thu Nov 28, 2013 3:50 am    Post subject: |   |  |  
		  |  Grand Master
 
 
 Joined: 17 Nov 2005Posts: 1002
 Location: New Zealand
 
 | 
			  
				| errno 104 is ECONNRESET which is 'connection reset by peer' I believe. This means that 'the other side' closed the socket on you. Now, this could be becauise a channel or Queue Manager ended abruptly or it could mean that your firewall just had enough of the socket and decided to end it. That's the beauty of networking that it's not always easy to know who did what and why ? 
 The starting point is probably to look at the error logs of BOTH ends. If they both say ECONNRESET (or similar) then the guy in the middle (firewall, router etc) probably did you in. If one of them says you ended the machine or there was a power cut or the cleaner unplugged the server to do some hoovering then it's probably just a glitch (mind you - might be worth having a word with the cleaner),
 
 Cheers,
 Paul.
 _________________
 Paul Clarke
 MQGem Software
 www.mqgem.com
 |  |  
		  | Back to top |  |  
		  |  |  
		  | jim | 
			  
				|  Posted: Thu Nov 28, 2013 4:44 am    Post subject: |   |  |  
		  | Voyager
 
 
 Joined: 26 Nov 2013Posts: 94
 
 
 | 
			  
				| 
   
	| PaulClarke wrote: |  
	| errno 104 is ECONNRESET which is 'connection reset by peer' I believe. This means that 'the other side' closed the socket on you. Now, this could be becauise a channel or Queue Manager ended abruptly or it could mean that your firewall just had enough of the socket and decided to end it. That's the beauty of networking that it's not always easy to know who did what and why ? 
 The starting point is probably to look at the error logs of BOTH ends. If they both say ECONNRESET (or similar) then the guy in the middle (firewall, router etc) probably did you in. If one of them says you ended the machine or there was a power cut or the cleaner unplugged the server to do some hoovering then it's probably just a glitch (mind you - might be worth having a word with the cleaner),
 
 Cheers,
 Paul.
 |  
 thanks paul
 
 in google search I got the link
 
 http://blog.techstacks.com/2012/10/bigip-fixing-mq-read-and-write-104-x68-errors.html
 |  |  
		  | 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
 
 |  |  |  |