Fixes are available
APAR status
Closed as program error.
Error description
In doubt transactions remain in DB2 when a WebSphere MQ classes for base java application that is performing an XA Transaction between WebSphere MQ and a DB2 database has the queue manager which it is connected to (which is also acting as the Transaction Manager) killed (intentionally or through a crash) mid transaction and before the WebSphere MQ Commit call is made. When the queue manager recovers, all WebSphere MQ work is successfully rolled back, however the database transaction remains in an in-doubt state.
Local fix
Local Fix￘ None
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere MQ classes for Java, which are making use of XA Transactions with WebSphere MQ and any XA enabled database where the database and WebSphere MQ work are being performed within the same transaction. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java +Java zOS **************************************************************** PROBLEM SUMMARY: A WebSphere MQ classes for Java application which uses a queue manager as the Transaction Manager, and DB2 as a Resource Manager in order to work with XA Transactions for the purpose of assuring data integrity between WebSphere MQ and DB2, experiences a queue manager outage whilst a transaction is in progress. Neither of the resources were able to commit the WebSphere MQ or database work that was performed in the transaction, and the WebSphere MQ work was rolled back successfully. However the database transaction remains in an in-doubt state.
Problem conclusion
In order to have the XA enabled database rollback the in-doubt transactions, the WebSphere MQ classes for Java needs to pass in a XATimeout parameter to the database when the JDBC Connection was obtained. This parameter causes any XA Transactions to rollback after the defined time out period, for example after 90 seconds. Prior to the code change associated with this APAR, the WebSphere MQ classes for Java did not offer any way of setting this parameter. To enable and configure this transaction time out value, a new WebSphere MQ classes for Java JVM System Property has been created: . com.ibm.mq.jdbc.XATransactionTimeoutPeriod This property takes as a value an integer number which represents the value in seconds. It can be configured as a JVM startup argument - for example to set it to use the value of 90 seconds, the JVM argument would be: . -Dcom.ibm.mq.jdbc.XATransactionTimeoutPeriod=90 --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.10 -------- -------------------- Windows U200352 AIX U853055 HP-UX (PA-RISC) U853082 HP-UX (Itanium) U853087 Solaris (SPARC) U853083 Solaris (x86-64) U853089 iSeries 7.0.1.10 Linux (x86) U853084 Linux (x86-64) U853088 Linux (zSeries) U853085 Linux (Power) U853086 zOS 7.0.1.10 v7.1 Platform Fix Pack 7.1.0.3 -------- -------------------- Windows 7.1.0.3 AIX 7.1.0.3 HP-UX (Itanium) 7.1.0.3 Solaris (SPARC) 7.1.0.3 Solaris (x86-64) 7.1.0.3 iSeries 7.1.0.3 Linux (x86) 7.1.0.3 Linux (x86-64) 7.1.0.3 Linux (zSeries) 7.1.0.3 Linux (Power) 7.1.0.3 zOS 7.1.0.3 Platform v7.5 -------- -------------------- Multiplatforms 7.5.0.1 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
IC86357
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-05
Closed date
2012-09-28
Last modified date
2012-09-28
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 WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R701 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023