Name: PK34624
=============
 
Summary:
   Reduce logging of ConcurrentModificationExceptions
 
Problem Description:
   Apply this fix if the Portal log file shows a lot of stack traces related to exceptions like 
   com.ibm.wps.util.ConcurrentModificationException: EJPDB0030E: Database has been changed since creation of data object [ObjectID = 9_0_1XXX [USER:12345]].
   As this exception is expected in certain scenarios under load, the fix changes the logging behavior to only log the message to make the Portal log file more readable.
   
 
Problem Solution:
   By multiple logins of the same user there is a high risk of ConcurrentModificationExceptions on the datastore layer, and these cause that the stack trace is written to the System.out log several times. This causes a log pollution that can be provoked by many logins. To fix this, the Datastore team added a new method to store data objects without logging the complete stack trace in case of ConcurrentModificationExceptions. The code for login, session timeout and session suspend handling was changed to use this new method and not to log the stacktrace a second time, but only log the message for this case.
 
Failing Module(s):
   Database
 
Affected Users:
   All users
 
Version Information:
    Portal Version(s): 5.1.0.4
     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.