Fix (APAR):  PK15310

Status:  Fix

Release:  5.1.1.7

Operating System:  AIX,HP-UX,Linux,Linux Red Hat - pSeries,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK15310

Byte size of APAR:  64627

Date: 2006-04-25

Abstract:  When an InvalidationById event is received via Data Replication Service (DRS), it is first deserialized using the system classloader and if that fails it is deserialized using the 

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

ERROR DESCRIPTION:                                              
Introduces a system property which determines which             
classloader to use first while deserializing an object. This way
customers can decide whether to use this  property or not based 
on their                                                        
scenario.                                                       

LOCAL FIX:                                                      
Added feature                                                   

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Application Server
with replication enabled

PROBLEM DESCRIPTION:
When an InvalidationById event is
received via Data Replication Service
(DRS), it is first deserialized using
the system classloader and if that
fails it is deserialized using the
application classloader. Since it is
a 2-step process it results in an
impact on performance.

RECOMMENDATION:
None

Deserializing the InvalidationEvent using system classloader
first and then using application classloader if that fails
causes an impact on performance.  This apar introduces a
system property  which determines which classloader to use
first while deserializing an object. This way customers can
decide whether to use this  property or not.

PROBLEM CONCLUSION:                                             
Using appropriate classloader when deserializing the            
InvalidationEvent helps improve the performance. This apar      
defines a system property,                                      
com.ibm.ws.cache.CacheConfig.useServerClassLoader, which lets   
customers decide which                                          
classloader to use when deserializing the InvalidationEvent.    
This property is set on the JVM (administrative console -> your 
server -> process definition -> JVM -> Custom property) and     
takes a boolean value. If set to 'true' server classloader is   
used to deserialize the InvalidationEvent otherwise application 
classloader is used.                                            
                                                                
The fix for this APAR is currently targeted for inclusion       
in cumulative fix 5.02.17, 5.1.1.9 and fixpack 6.0.2.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
___  ___ 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: