Fix (APAR):  PK12081

Status:  Fix

Release:  5.1.1.6,5.1.1.5,5.1.1.4,5.1.1.3,5.1.1.2,5.1.1.1,5.0.2.9,5.0.2.8,5.0.2.13,5.0.2.12,5.0.2.11,5.0.2.10

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  PK10997

CMVC Defect:  PK12081

Byte size of APAR:  13718

Date: 2005-10-13

Abstract:  Caching an .html file with consume-subfragment=true on its parent is throwing exceptions

Description/symptom of problem:  

PK12081 resolves the following problem:

ERROR DESCRIPTION:                                              
If html is cached as a child with consume-subfragment = true.   
The following exception is throw:                               
                                                                
com.ibm.commerce.struts.ECActionServlet processRequest          
CMN0420E: The following command exception has occurred          
during processing:                                              
"java.lang.IllegalStateException: Writer already obtained".     
java.lang.IllegalStateException: Writer already obtained        
at                                                              

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Application Server
using the 'consume-subfragments' feature of
servlet caching

PROBLEM DESCRIPTION:
Caching an .html file with
consume-subfragment=true on its
parent is throwing exceptions

RECOMMENDATION:
None

When an .html is included in a jsp using c:import and
consume-subfragment=true on the jsp, an illegalStateException
is thrown when accessing the jsp with servlet caching enabled

PROBLEM CONCLUSION:                                             
The content is now displayed fine without any exceptions when   
an .html is included in a jsp using c:import with               
consume-subfragment=true on the jsp.                            
                                                                
The fix for this APAR is currently targeted for inclusion       
in 5.02.14, 5.1.1.8 and 6.0.2.5.                                
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: