Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
Virtual member manager (VMM) joins a transaction if one is in progress, otherwise it creates a new one. If an exception occurs at any point during the API call(such as get, search, create, update, delete, etc..), the transaction fails and may be rolled back. VMM should provide support to suspend the active Global Transaction, and create a new one internally before calling each of the VMM API's. So, when any call fails, the global transaction of the caller will remain intact.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 Virtual member * * manager (VMM) * **************************************************************** * PROBLEM DESCRIPTION: VMM rollsback global transaction when * * a VMM ServiceProvider API call throws * * an exception back to the caller * **************************************************************** * RECOMMENDATION: * **************************************************************** VMM ServiceProvider API calls such as GET, SEARCH, LOGIN, UPDATE, CREATE, etc.. currently use active global transactions. So when any VMM operation fails internally, it marks the global transaction for rollback. VMM cannot determine if the transaction succeeded or failed based on the exception received.
Problem conclusion
A new property "useGlobalTransaction" has been added to the "contexts" DataObject, which is part of the input DataObject while invoking the VMM API. When this property value is set to false then VMM creates a NEW transaction internally, so no global transaction is affected. If the property is not defined or its value is set to true, then the behavior is as it previously was. VMM will not create new transaction for the API calls. This fix is applicable for all VMM APIs. Sample code with 'useGlobalTransaction' property defined: DataObject root = SDOHelper.createRootDataObject(); /* Set 'useGlobalTransaction=false' in the context dataobject and instruct VMM to create a new transaction for invoking the VMM API */ DataObject contexts = root.createDataObject(DO_CONTEXTS); // DO_CONTEXTS = "contexts" contexts.set("key", "useGlobalTransaction"); contexts.set("value", "false"); .... DataObject entity = SDOHelper.createEntityDataObject(root, null, SchemaConstants.DO_GROUP); entity.createDataObject(SchemaConstants.DO_IDENTIFIER).set(Schem aConstants.PROP_UNIQUE_NAME, principalDN); .... //Inside PrivilegedExceptionAction.run() Service service = new LocalServiceProvider(null); return service.get(root); The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.7, 8.5.5.1. 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
PM89827
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-05-27
Closed date
2013-08-09
Last modified date
2013-08-09
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
12 January 2022