Fixes are available
APAR status
Closed as program error.
Error description
Using WebSphere MQ v7, along with WebSphere Process Server v6, WebSphere Application Server v6, and WebSphere Message Broker v7, attempts are made to establish a High Availability setup. WebSphere MQ V7 JMS application is reporting the connection Manager received a fatal connection error from the Resource Adapter. The following error message is being recorded: J2CA0056I: TheConnection Manager received a fatal connection error from the Resource Adapter for resource <RESOURCE>. The exception which was received is com.ibm.msg.client.jms. DetailedJMSException: JMSWMQ1107: A problem with this connection has occurred. An error has occurred with the WebSphere MQ JMS connection. Use the linked exception to determine the cause of this error.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN').: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009:com.ibm.mq.jmqi. JmqiException: CC=2;RC=2009;AMQ9208: Error on receive from host '<host name>/<ip address>:<port number> (<host name>)'.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of WebSphere MQ V7 classes for JMS and classes for Java who make use of channel send exits and XA. This includes users of WebSphere Application Server that use WebSphere MQ messaging. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: The WebSphere MQ V7 classes for JMS and classes for Java may cause communication data inconsistencies when used with send exits. This results in invalid data being transmitted to the queue manager, which terminates the connection as a result.
Problem conclusion
The WebSphere MQ V7 classes for JMS and classes for Java have been updated to prevent the data inconsistencies occurring and leading to a broken connection. The MQRC_CONNECTION_BROKEN (2009) reason code continues to be used validly in situations where network communications between the queue manager and WebSphere MQ classes for Java/JMS client are interrupted or terminated unexpectedly. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.1.6 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IV00348
Reported component name
WMQ AIX V7
Reported component ID
5724H7221
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-11
Closed date
2011-06-02
Last modified date
2014-06-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ AIX V7
Fixed component ID
5724H7221
Applicable component levels
R701 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1"}]
Document Information
Modified date:
27 September 2021