PQ95907: CUSTOM PROPERTY FOR XA RESOURCES WHICH HINTS TO THE TRANSACTION MANAGER TO COMMIT THIS RESOURCE LAST IN A TRANSACTION.

 Fixes are available

5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux



APAR status
Closed as program error.

Error description
In a distributed transaction, it is not possible to guarantee
the intermediate state of any resources enlisted in the
transaction.  It is also not guaranteed that resources in a
transaction will be committed in the same order that they were
listed.

This APAR includes a custom property which can be defined on the
XA resource which will hint to the Transaction Manager that this
resource should be committed last in the transaction.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users with JVM  *
*                 custom property CommitJMSTransactionsLast    *
****************************************************************
* PROBLEM DESCRIPTION: Application Server does not guarantee   *
*                      the order of committing of enlisted     *
*                      resources                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Application Server does not allow for a specified ordering for
committing of enlisted resources - with JMS resources associated
with queues with event triggers, this can cause an action to be
done on other resources that are taking part within the same
transactions, but have not yet been committed.
Problem conclusion
Optionally allow JMS resources to be committed last, behind
all other enlisted, non-JMS, resources.
The fix for this APAR is currently targeted for inclusion in
fixpack 5.1.1.4. Please refer to the Recommended Updates page
for delivery dates:

http://www-1.ibm.com/support/docview.wss?rs=180&
context=SSEQTP&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PQ95907
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-10-19
Closed date 2005-01-11
Last modified date 2005-01-11

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJS          

Publications Referenced

Fix information

Applicable component levels
R003 PSN    UP
R00A PSN    UP
R00H PSN    UP
R00I PSN    UP
R00P PSN    UP
R00S PSN    UP
R00W PSN    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ95907
IBM Group: Software Group
Modified date: Jan 11, 2005