PK61666: WEBSPHERE APPLICATION SERVER FOR Z/OS IS UNABLE TO RECOVER WITH XA RESOURCES AFTER XA TRANSACTION LOGS ARE MOVED TO A LOGSTREAM | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When the XA partner log of a WebSphere Application Server for z/OS server instance is located in an MVS logstream, the XA resources participating in the transaction may not recover correctly in the event of a failure. The default location for the XA partner log is the HFS. The symptoms of this condition will vary by resource manager. Often, the resource manager will hold locks after the failure, and this is detected by the application after the servers are restarted. Transaction branches represented by these XA resources may need to be recovered manually by an operator. The procedure for doing this varies by resource manager.Local fix The XA partner log should be moved back to the HFS until the PTF resolving this APAR is applied.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V6.1 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS * * may not be able to recover with XA * * resource managers when the XA partner * * log is located in a logstream. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere Application Server for z/OS writes the information needed to re-connect to XA resource managers in the XA partner log. These log entries are used during transaction recovery to resolve transaction branches which are in-doubt. The log entries are indexed with an 8-byte identifier. The log can be written to the HFS or to an MVS logstream. When writing to a logstream, the 8-byte identifier could be truncated. If the log identifier is truncated, WebSphere will be unable to automatically resolve transaction branches which are in-doubt. The transaction branches must be resolved manually. This can effect both Peer Restart and Recovery (PRR) and recovery using the High Availability Manager. The method for detecting the failure varies by resource manager. Often, a resource will remain locked and will be detected by the application. In the event of a database, rows of the database may remain locked and prevent new updates from completing. Similarly, the method for manually recovering varies by resource manager.Problem conclusion Code was added to ensure the log identifiers used by the XA partner log are not truncated when written to a logstream. APAR PK61666 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.17 of WebSphere Application Server V6.1 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PK61752 Modules/Macros Publications Referenced
|
Document Information |
Current web document: swg1PK61666.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 610
Software edition:
Reference #: PK61666
IBM Group: Software Group
Modified date: Jul 2, 2008
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.