Fix (APAR):  PK17095

Status:  Fix

Release:  6.0.2.5

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

Supersedes Fixes:  

CMVC Defect:  PK17095

Byte size of APAR:  143724

Date: 2006-06-16

Abstract:  When request or response objects are not cloned properly and they are reused, this leads to corruption in context objects.

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

ERROR DESCRIPTION:                                              
Portal code does not clone contexts correctly.  Showed how a    
similar issue with customer custom code could do the same.      

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Application Server version
6.0.2 users who try to use threading
to do include or forward by reusing their
request and response objects

PROBLEM DESCRIPTION:
When request or response objects are
not cloned properly and they are
reused, this leads to corruption in
context objects.

RECOMMENDATION:
None

When request or response objects are not cloned properly and
they are reused, this leads to corruption in context objects.
Resultant behaviour will be that one can view data from other
requests. Data viewed by the customer will be corrupted as
well. Currently clone is used only by IBM stack products.

This problem was happening because of improper handling of
context objects.


PROBLEM CONCLUSION:                                             
The problem was corrected by making sure the context object is  
renewed for every request and in case an old context object     
gets corrupted, create a new one.                               
                                                                
The fix for this APAR is currently targeted for inclusion       
in 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 6.0
_x Application Server (Express or BASE)
_x Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)

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

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

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

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

1) Copy PKxxxxx.pak 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.pak file which was copied in the maintenance 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.pak).

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:  This iFix also contains the fixes for PK22392 and PK18815