Name: PK38575
=============
 
Summary:
   Out-of-memory error due to state document nodes in object pools
 
Problem Description:
   In scenarios under high load with multiple portlets using long state values, portal might
   run out of memory due to the state document nodes stored in object pools.
   The problem is that these nodes are put back into their object pool without clearing their
   node values. Under high load the object pool contains a lot of nodes consuming a lot
   of memory due to their node values.
   
 
Problem Solution:
   Fix makes sure that values of document nodes are cleared before putting the nodes
   back to their object pool.
   
 
Failing Module(s):
   Engine: State handling
 
Affected Users:
   All users
 
Version Information:
    Portal Version(s): 6.0.0.0
     Pre-Requisite(s): 
      Co-Requisite(s): ---
 
Platform Specific:
   This fix applies to all platforms.
 
Installation:
   NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
          The Portal Update Installer can be downloaded from the following link:
          http://www.ibm.com/software/genservers/portal/support
 
   1. Create temporary "fix" directory to store the jar file.
   2. Copy jar file to this directory.
   3. Shutdown WebSphere Portal.
   4. Follow the fix installation instructions that are packaged with
      the Portal Update Installer on how to install the fix.
   5. Restart WebSphere Portal.
   6. The temporary directory may be removed.
 
Un-Installation:
   NOTE:  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.
 
   1. Shutdown WebSphere Portal.
   2. Follow the instructions that are packaged with the
      Portal Update Installer on how to uninstall the fix.
   3. Restart WebSphere Portal.