eFix (APAR): pq59932
Status:      eFix

Release: WebSphere 4.0.2,4.0.3

Operating System: all

Supersedes eFixes: none 

Required eFixes: 
PQ58795 abstract: PQ53588 CAUSES AN OBJECT/STRING CONVERSION PROBLEM IN JSP TAG LIBRARY EXTENSION


CMVC defect: PQ59932 

Byte size of APAR: 885,727 bytes

Date: 04/09/02


Abstract: TRY/FINALLY BLOCKS FOR JSP CUSTOM TAGS ARE CAUSING PERFORMANCE PROBLEMS DURING GARBAGE COLLECTION USING SOLARIS JDK 1.3.0/1.3.1
  

Description/symptom of problem:

 The problem appears to be the way that the JVM classloader handles      
 nested blocks.                                                  
 Factors that affect the bug are:                                
 1)How deeply nested the blocks are.                             
 2)The number of try/catch blocks.                               
 3)The complexity of the try/catch blocks.                       
 The memory usage is exponential.                                
 Garbage collection also appears to be effected.                 
 When the blocks were flattened out the GC times went away.      

  


Directions to apply efix:

1) Create temporary "efix" directory to store the jar file:
             AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
         Windows: c:\temp\WebSphere\efix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>

5) Clear the contents of <WASHOME>/temp

6) Restart WebSphere

7) The temp directory may be removed but the jar file should be saved.  Do not remove 
   any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/<efix> directories.
   These files are required if an efix is to be removed.



Directions to remove an efix:

NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN EFIX UNLESS
       ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be
          removed, efix3 must be removed first, efix2 removed, and efix3 re-applied.


1) Change directory to the efix location (<WASHOME>/WebSphere/AppServer/efix/<efix#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar <backup_efix#>

4) Restart WebSphere



Directions to re-apply an efix:

Follow the instructions for applying an efix.  If the backup files still exist (from the 
previous efix application), you will be prompted to overwrite.  Answer "yes" at the overwrite 
prompts.



Additional Information:
------------------------------------------------------------------