PK87205: MESSAGES CAN BE LEFT UNCOMMITTED ON A WEBSPHERE MQ QUEUE

Fixes are available

APAR status

Closed as program error.

Error description

Messages on a WebSphere MQ queue can be left uncommitted, as
part of an indoubt XA transaction coordinated by WebSphere
Application Server, after a queue manager restart.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  Version 6.1 and Version 7.0 using           *
*                  WebSphere MQ as a JMS messaging provider    *
****************************************************************
* PROBLEM DESCRIPTION: Messages might be left uncommitted on   *
*                      a WebSphere MQ queue as part of an      *
*                      indoubt XA transaction that is never    *
*                      resolved, after a queue manager         *
*                      restart or network error.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In certain circumstances a failure to commit or rollback
a send or receive of a WebSphere MQ message is incorrectly
suppressed by the WebSphere MQ messaging provider code within
the application server.
This is most likely to occur when a queue manager is stopped
and restarted while transactions within the application server
are active, or if a network connection to a queue manager
fails.
The incorrect suppression of the failure causes the
transaction manager to assert that the commit or rollback was
successful. Consequently, the resolution of the transaction is
never retried and the message in WMQ remains uncommitted until
the transaction is manually resolved (using the rsvmqtrn
WebSphere MQ control command).

Problem conclusion

This fix ensures that commit/rollback failures are reported to
the transaction manager so it retry the operation 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

Manual resolution of the XA transaction branch in WebSphere MQ
is required for any transactions stuck in-doubt.  The
programming error addressed by this APAR means that it is not
possible for either WebSphere Application Server or WebSphere
MQ to know the correct outcome for the transaction once the
problem has occurred.

Correct transaction completion direction is vital to avoid
message duplication or loss.  To choose the transaction
completion direction, the application data must be considered
carefully.

For example, rollback of a transaction including a receive of
a message by a message-driven would return the message to the
WebSphere MQ queue, causing it to be replayed. If other
actions performed by the message-driven bean (such as a
database update) had been successfully committed, then rolling
back the transaction could cause duplication, so the correct
action would be to commit the transaction so that the message
would not be replayed.

Comments

APAR Information

APAR number
PK87205
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-22
Closed date
2009-06-30
Last modified date
2014-05-20

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK87205: MESSAGES CAN BE LEFT UNCOMMITTED ON A WEBSPHERE MQ QUEUE

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?