PK86779: SIB MESSAGE LOCKED WITH XID INDEFINITELY

Fixes are available

APAR status

Closed as program error.

Error description

If a connection to a messaging engine closes while a transaction
is committing, there is a timing window in which a message
involved in that transaction can be locked by an XID
indefinitely.  In order for this to occur, the transaction must
be prepared and the connection to the messaging engine must
close before the commit can be issued.  The SIB XAResource
will tell the transaction manager that the transaction has
been rolled back, preventing the server from finishing the
commit on restart.

Local fix

```
No workaround is available.
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server            *
*                  Version 6.1 and Version 7.0                 *
****************************************************************
* PROBLEM DESCRIPTION: If a connection to a messaging engine   *
*                      closes while a transaction is           *
*                      committing, there is a timing           *
*                      window in which that transaction        *
*                      remains indoubt within the messaging    *
*                      engine indefinitely                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The issue occurs when the transaction manager has successfully
completed the prepare phase of a two-phase commit, and the
network connection to the messaging engine breaks before the
commit (or rollback) phase of the two-phase commit completes.

The XAResource for the messaging engine incorrectly informs the
transaction manager that the transaction has been rolled
back, even though the messaging engine could not be contacted
and would not automatically rollback a transaction that is
indoubt (has completed prepare).
This leaves the transaction indoubt within the messaging
engine, until it is manually resolved by an administrator
using the instructions in the "Resolving indoubt transactions"
section of the WebSphere Application Server information center.

The exception that causes this issue is an XAException with
errorCode XA_RBROLLBACK thrown from the commit or rollback
methods of the following class:
com.ibm.ws.sib.comms.client.OptimizedSIXAResourceProxy

Problem conclusion

This fix for this APAR throws an XAException with the
correct errorCode (XAER_RMFAIL) from commit or rollback if the
transaction has been prepared, so that the transaction manager
will retry the commit/rollback later.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.27 and 7.0.0.7.  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK86779
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-15
Closed date
2009-06-05
Last modified date
2009-06-05

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
PLAT MSG COM
Fixed component ID
620600101

Applicable component levels

R200 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK86779: SIB MESSAGE LOCKED WITH XID INDEFINITELY

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R200 PSY

Document Information

Share your feedback

Need support?