eFix (APAR): pq54167 

Status:      efix 

For Release: WebSphere 4.0.1, 4.0.2

For Edition: WebSphere AE, AEs

For ContainerTypes: All

For Operating System: All

Supersedes eFixes:  N/A

CMVC defect: PQ54167 

Byte size of APAR: 878,227 bytes

Date: 11/05/01

Abstract: Option A Caching not working correctly

Description/symptom of problem: 
Although Option A caching is in effect for an EJB it can
be seen that every time a method call is made on the bean, an ejbLoad() is being issued.
This is because during after_completion processing a rollbackBean() request is being
issued, so the bean is removed from the cache when it should not be. 

Directions to apply efix:

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

2) Copy zip/tar file to the directory

3) Unzip/untar the file

4) Shutdown WebSphere

5) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar PQ54167_eFix_all.jar

6) Restart WebSphere

7) The temp directory may be removed but the zip/tar file should be saved.  Do not remove 
   any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/<PQ54167> 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/<PQ54167>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar PQ54167_eFix_all_backup.jar

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.


Trouble shooting
--------------------------------------------------------------------------------------
o  If an efix complains about the container type and you are sure it should match, contact
   WebSphere L2 Support for assistance with the -SkipContainerCheck option to the efix jar.

o  If the efix complains about the version of XML parser, move the file 
   $WASROOT/jre/lib/ext/xerces.jar to a temporary location (such as c:\temp), load the efix 
   and move the file back to it's original location.