Fix (APAR):  PK13701

Status:  Fix

Release:  5.1.1.7,5.1.1.6,5.1.1.5,5.1.1.4,5.1.1.3

Operating System:  AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  9457

Date: 2005-12-19

Abstract:  ClassCastException is thrown and message WTRN0040W is produced during server startup

Description/symptom of problem:  
 
PK13701 resolves the following problem:

ERROR DESCRIPTION:                                              
The buildRecoveryClassLoader method is trying to cast the       
customers classloader as a WsClassLoader and is failing         
                                                                
                                                                
XARecoveryDat > buildRecoveryClassLoader                        
com.odcgroup.otf.services.utils.CompoundClassLoader@179d425     
                                                                
XARecoveryDat E WTRN0040W: Object cannot be deserialized.       
The exception stack trace follows:                              
java.lang.ClassCastException at                                 
com.ibm.was.Transaction.JTA.XARecoveryData.buildRecoveryClassLoa
der(XARe                                                        
c                                                               
overyData.java:425)                                             

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
All WebSphere Application Server version 5.1
users.

PROBLEM DESCRIPTION:
ClassCastException is thrown and
message WTRN0040W is produced during
server startup

RECOMMENDATION:
None

ClassCastException is thrown and message WTRN0040W is produced
by method buildRecoveryClassLoader in XARecoveryData during
server startup. This is caused by the class attempting to cast
each of the chain of classloaders into WsClassLoader. In this
instance the classloader the attempt is being made on, is not
supplied by WebSphere Application Server and so is not a
subclass of WsClassLoader, which results in the
ClassCastException.

PROBLEM CONCLUSION:                                             
XARecoveryData has been changed to ensure that the cast is only 
performed when the classloader is an instance of WsClassLoader. 
The fix for this APAR is currently targeted for inclusion in    
fixpack 5.1.1.9. Please refer to the Recommended Updates page   
for delivery information:                                       
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  
NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release:
5.0  5.1
___  X__ Application Server (Express or BASE)
___      Enterprise Edition (DD)
___  ___ Network Deployment (ND)
___  ___ Edge Components
___  ___ Developers Edition
___  ___ Tools
     ___ WebSphere Business Integration Server Foundation (WBISF)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
__ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory.
It uses fixpacks and fixes as the location of the unpacked files.

1) Copy PKxxxxx.jar file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PKxxxxx.jar file which was copied in the maintenance directory).
The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory.

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  
NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PKxxxxx.jar).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.



Additional Information: