Mq Error 68
Contents |
RSS Feed - WebSphere MQ amq9206 Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » General IBM MQ Support » TCP/IP read() call was 104 (X'68')Tcp Return Code 104
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
Amq9999
104 (X'68') VoyagerJoined: 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 amq9209 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 CouncilJoined: 10 Feb 2003Posts: 5826Location: 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
Re: TCP/IP error (X'68') with MQ Client Channel Newsgroups: gmane.network.mq.devel Date: Friday 14th August 2015 00:49:10 UTC (about 1 year ago) Tim - Thanks for the information. From: MQSeries List [mailto:[emailprotected].org] On Behalf Of Tim Zielke Sent: Thursday, August 13, 2015 3:11 PM To: [emailprotected].org Subject: Re: TCP/IP error (X'68') with MQ Client Channel Hi Lawrence, FYI - I was working another issue yesterday and noticed a similar error about a 104 (ECONNRESET) on the queue manager side. Here is what I observed. On the MQ Client server side (Linux), I saw the JVM produce the following error: Aug 12 22:45:11 server1 IBM Java[23573]: JVMDUMP039I Processing dump event "systhrow", http://www.mqseries.net/phpBB2/viewtopic.php?p=367101&sid=6b0032c660db0b9dc0d836af010a707d detail "java/lang/OutOfMemoryError" at 2015/08/12 22:45:11 - please wait. 30 seconds later, I saw the following in the queue manager error log (also Linux): 08/12/2015 10:45:41 PM - Process(22867.6976) User(mqm) Program(amqrmppa) Host(server2) Installation(Installation1) VRMF(7.5.0.4) QMgr(QM1) AMQ9206: Error sending data to host server1 (123.123.123.123). EXPLANATION: An error occurred sending data over TCP/IP to server1 (123.123.123.123). This may be due to a communications failure. ACTION: The return code from the TCP/IP(write) http://permalink.gmane.org/gmane.network.mq.devel/19480 call was 104 X('68'). Record these values and tell your systems administrator. The MQ Client application on server1 was a multi-threaded application, so I am pretty sure the process continued to run when that thread that threw the "java/lang/OutOfMemoryError" probably died. So maybe this behavior (or at least one use case for it) might have to do with when an MQ Client application abnormally loses a thread that is using a channel, and then when the queue manager side tries to reference the channel, it causes the TCP socket on the MQ Client server end to realize that the thread is gone and then the TCP stack on the MQ Client server side sends a TCP RST to the TCP stack on the queue manager server side and then this queue manager error of a ECONNRESET is reported. Definitely a guess on my part, but wanted to pass this observation on. So basically, the result of a multi-threaded MQ Client having a thread abnormally terminate that is using an MQ client channel. Thanks, Tim Tim Zielke | CICS/MQ Systems Programmer Aon Service Corporation | Aon Technology | Foundational Technologies 4 Overlook Point, Lincolnshire, IL 60069 t +1.847.295.5000 [emailprotected]
application. I have Googled this x'68' TCP error, but my limited knowledge of TCP is preventing me from making any sense of this error. I http://mqseries.listserv.meduniwien.ac.narkive.com/JMElgqTJ/weird-tcp-ip-error-with-client-channel am not too stressed about this error since I will be upgrading this server in a couple of weeks, but it just drives me nuts to not http://stackoverflow.com/questions/31825440/websphere-mq-connection-error be able to understand what could be causing this error. The MQServer is 6.0.2.10(I know, I know.......).Can someone shed any light on this TCP error code as mq error it pertains to a MQ Client connection?errno 68: EADDRNOTAVAIL 68 Can't assign requested address************************************************************************************************************************************04/19/2014 07:18:14 PM - Process(19699.699) User(mqm) Program(amqrmppa)AMQ9208: Error on receive from host 189 (189.179.149.40).EXPLANATION:An error occurred receiving data from 189 (189.179.149.40) over TCP/IP. Thismay be due to a communications failure.ACTION:The return code from the TCP/IP (read) call was 104 (X'68'). Record thesevalues mq error 68 and tell the systems administrator.This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you.To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,in the message body (not the subject), write: SIGNOFF MQSERIESInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Ian Alderson 2014-05-20 08:05:25 UTC PermalinkRaw Message Hi Lawrence,I usually see AMQ9208 error when an application has terminated without cleanly disconnecting from the Queue Manager. E.g. someone kills a client app instead of letting it end gracefully or an application hits some logic where it simply does not attempt to disconnect before ending. Less commonly it could also be caused by a network error which would see more widespread problems.If you really want to look up TCP error codes, then you need to
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Websphere Mq Connection error up vote 2 down vote favorite When I run the following program it give me the jms.DetailedJMSException: JMSWMQ2020: Failed to connect to queue manager '' with connection mode 'Client' and supplied CCDT URL. Can somebody please help me to run this program.. MQQueueConnectionFactory cf = new MQQueueConnectionFactory(); // Config cf.setHostName("192.163.1.173"); cf.setPort(1414); cf.setTransportType( JMSC.MQJMS_TP_CLIENT_MQ_TCPIP); cf.setQueueManager("TEST"); cf.setChannel("SYSTEM.DEF.SVRCONN"); MQQueueConnection connection = (MQQueueConnection) cf.createQueueConnection("mgm","mgm321"); MQQueueSession session = (MQQueueSession) connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); MQQueue queue = (MQQueue) session.createQueue("queue:///QUEUE4"); MQQueueSender sender = (MQQueueSender) session.createSender(queue); MQQueueReceiver receiver = (MQQueueReceiver) session.createReceiver(queue); long uniqueNumber = System.currentTimeMillis() % 1000; JMSTextMessage message = (JMSTextMessage) session.createTextMessage("SimplePTP "+ uniqueNumber); // Start the connection connection.start(); sender.send(message); System.out.println("Sent message:\\n" + message); JMSMessage receivedMessage = (JMSMessage) receiver.receive(10000); System.out.println("\\nReceived message:\\n" + receivedMessage); sender.close(); receiver.close(); session.close(); connection.close(); This is the stack trace of the error.. com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2020: Failed to connect to queue manager '' with connection mode 'Client' and supplied CCDT URL 'http://192.168.1.173', see linked exception for more information. Check the queue manager is started and if running in client mode, check there is a listener running. Please see the linked exception for more information. at com.ibm.msg.client.wmq.common.internal.