Amq9208 Mq Error
Contents |
a WMQ client channel connection to a local server AMQ9206 10054(X'2746') econreset econnreset amq6184: an internal websphere mq error has occurred on queue manager from tcp/ip client channel Technote (troubleshooting) Problem(Abstract) You are receiving an
Amq6119: An Internal Websphere Mq Error Has Occurred
error 10054 (X'2746') econnreset intermittently from TCP/IP on a WebSphere MQ (WMQ) client channel connection to
Amq6109: An Internal Websphere Mq Error Has Occurred.
a local server. Symptom AMQ9208: Error on receive from host
Amq6125: An Internal Websphere Mq Error Has Occurred
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. For WMQ 7.1.0, the same scenario results in: AMQ9209: Connection to host
AND GET FDCS WITH XC130003 AND RM031101 Fixes are available WebSphere MQ V7.0 for i5/OS Fix Pack 7.0.0.1 WebSphere MQ V6.0 Fix Pack 6.0.2.5 WebSphere MQ V7.0 for i5/OS Fix amq8101 websphere mq error 893 has occurred Pack 7.0.0.2 WebSphere MQ V7.0 Fix Pack 7.0.0.1 WebSphere MQ V7.0 Fix Pack 7.0.0.2 amq9206 WebSphere MQ V7.0 Refresh Pack 7.0.1.0. WebSphere MQ V7.0 Fix Pack 7.0.1.1 WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.1 WebSphere amq9208 104 MQ V7.0 Fix Pack 7.0.1.2 WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.2 WebSphere MQ 6.0 for HP OpenVMS Alpha and Itanium - Fix Pack 6.0.2.7 WebSphere MQ 6.0 for HP OpenVMS Alpha and http://www-01.ibm.com/support/docview.wss?uid=swg21106218 Itanium - Fix Pack 6.0.2.10 (FP03) Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description WebSphere MQ channels terminated unexpectedly with messages AMQ9604: Channel terminated unexpectedly and AMQ9208: Error on receive from host xxxxxx EXPLANATION: An error occurred receiving data from xxxxx over TCP/IP. This may be due to a communications failure. ACTION: The return code from the TCP/IP (read) call http://www.ibm.com/support/docview.wss?uid=swg1IZ25614 was 104 (X'68'). . The FDC's show that rriAcceptSess calls are failing in the amqrmppa process with a SIGSEGV and we are getting probe id's XC130003 and RM031101. The function stack for both FDCs shows: MQM Function Stack ccxResponder rrxResponder rriAcceptSess xcsFFST Local fix Problem summary **************************************************************** USERS AFFECTED: This problem may be encountered when attempting to connect to a queue manager which has channel auto-definition set (the queue manager CHAD attribute set to ENABLED). Users with channel auto- definition enabled are recommended to disable it if it is not required; or else to ensure a fix for this APAR is applied. Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: The SIGSEGV FDCs in amqrmppa show that function rriGetChannelDef (called from rriAcceptSess) invoked lpiSPIKernel which returned arcE_OBJECT_NOT_FOUND (it did not find the requested channel). Routine rriGetChannelDef should have returned a failure code, but it returned OK. This immediately leads to a SIGSEGV in rriAcceptSess. Very careful examination of the code of rriGetChannelDef reveals that there is a failure path out of this function whereby it fails to set its return code correctly. Problem conclusion Corrected the coding to ensure that all exit paths out of function rriGetChannelDef set a return code appropriat
Tomcat 5.5.36 Released » 10/10/2012 BigIP: Fixing MQ Read and Write 104 X('68') Errors F5 published a Deployment Guide "Deploying the BigIP LTM with IBM WebSphere MQ", which provides a very good HowTo guide for load-balancing http://blog.techstacks.com/2012/10/bigip-fixing-mq-read-and-write-104-x68-errors.html MQ with a BigIP and provides all the steps necessary to get up and running quickly. I followed all these steps myself and my developers were off and running. The problems started a little later, https://groups.google.com/d/topic/ibm.software.websphere.mq.programming/sMA8jgWcClQ however, when the application was unable to read messages off of the queue. Errors like the following were showing up in the MQ "client" logs: AMQ9208: Error on receive from host 10.X.Y.Z (10.X.Y.Z). EXPLANATION: An mq error 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 websphere mq error 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. If the BigIP VIP was bypassed, the errors on both ends of the connection would go away. No firewalls separated one mq node from another. Other than citing a "network failure", IBM support wasn't much assistance here. Initial network traces indicated that I had not followed the deployment guide recommendations verbatim, as the traces were showing keep-alive requests every 300 seconds from the MQ nodes, which also matched the 300 second tcp idle timeout on the BigIP. It was somewhat easy to assume then that the bigip was issuing a connection reset on the idle tcp connection at around the same time the mq heartbeat was getting issued but reducing the MQ Heartbeat interval to below the BigIP's TCP Idle Timeout value did not resolve the issue. The resolution was found with the help from this F5 Solution Article: "SOL8049: Implementing TCP Keep-Alives for server-client communication using TCP profiles". Add a Keep Alive Interval to the TCP profile (or create a new tcp profile) and assign the value to half of what your tcp timeout is set to (or an even smalle
from GoogleSign inHidden fieldsSearch for groups or messages