PK61666: WEBSPHERE APPLICATION SERVER FOR Z/OS IS UNABLE TO RECOVER WITH XA RESOURCES AFTER XA TRANSACTION LOGS ARE MOVED TO A LOGSTREAM

 Fixes are available

6.1.0.17 WebSphere Application Server V6.1 Fix Pack 17 for i5/OS
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Linux
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Solaris
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for HP-UX
6.1.0.17: WebSphere Application Server V6.1 Fix Pack 17 for Windows
6.1.0.17 WebSphere Application Server V6.1 Fix Pack 17 for AIX
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for AIX platforms
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for HP-UX platforms
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Linux platforms
V6.0.2: Java SDK 1.4.2 SR11 Cumulative Fix for IBM WebSphere Application Server
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Solaris
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Windows platforms
6.1.0.19 WebSphere Application Server V6.1 Fix Pack 19 for AIX
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for HP-UX
6.1.0.19 WebSphere Application Server V6.1 Fix Pack 19 for i5/OS
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for Linux
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for Solaris
6.1.0.19: WebSphere Application Server V6.1 Fix Pack 19 for Windows
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for AIX platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for HP-UX platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for OS/400 platform
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Linux platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Solaris
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Windows platforms
V6.0.2: Java SDK 1.4.2 SR11 Cumulative Fix for IBM WebSphere Application Server



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 information
APAR number PK61666
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 610
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2008-02-25
Closed date 2008-03-05
Last modified date 2008-07-02

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

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSN    UP
R601 PSY    UP
R610 PSY UK36750    UP08/06/10 P F806

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


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