IBM MQ Channel Goes In Abend Due To Incorrect OSB XA Call Sequence
(Doc ID 2349804.1)
Last updated on SEPTEMBER 18, 2023
Applies to:
Oracle WebLogic Server - Version 12.2.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
On OSB 12.2.1.0, connecting via MQ Transport to MQ v7.1 (client 7.5.0.7) installed on z/os. MQ Channel, in a unpredictable way, sometime goes in abend state unexpectedly (it shutdown itself). This happen in different environments (Dev, test and reprod) and quite frequently.
IBM has analyzed the issue and in its report (attached) is stating the root cause is due to the client (OSB) that is sending to MQ an invalid sequence of XA commands in the same transaction: for the same XID, OSB sends multiple TMFAIL /TMSUCESS commands. OSB uses weblogic as transaction manager and call its API to do txn.commit() or txn.rollback(), which calls weblogic JTA API that performs XAResource.commit then XAResource.end().
The suspicious transaction end sequence is:
<Nov9, 2017 3:22:31 PM CET> <Debug> <JTAXA> <BEA-000000> <BEA1-30AEC5A6C39CEEA2D796: null: XA.end(rm=OSB__issp-sbc/issp-rt-sbc/Resources/MQConnection_2, xar=com.bea.wli.sb.resources.mqconnection.OSBMQXAResource@5fd1885f,flags=TMFAIL)>
<Nov 9, 2017 3:22:31 PM CET> <Debug> <JTAXA> <BEA-000000> <BEA1-30AEC5A6C39CEEA2D796: null: XA.end(rm=OSB__issp-sbc/issp-rt-sbc/Resources/MQConnection_2, xar=com.bea.wli.sb.resources.mqconnection.OSBMQXAResource@5fd1885f,flags=TMFAIL)>
<Nov 9, 2017 3:23:01 PM CET> <Debug> <JTAXA> <BEA-000000> <BEA1-30AEC5A6C39CEEA2D796: null:XA.end(rm=OSB__issp-sbc/issp-rt-sbc/Resources/MQConnection_2,xar=com.bea.wli.sb.resources.mqconnection.OSBMQXAResource@5fd1885f,flags=TMSUCCESS)>
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |