eFix (APAR): PQ57311

Status:

For Release: WebSphere 4.0, 4.0.1

For Edition: WebSphere AE, AEs

For ContainerTypes: All

For Operating System: all

Supersedes eFixes:  none

CMVC defect: 112841

Date: 1/30/2002

Abstract: Exception is reported when mulitple nodes with security are started, then one of them is stopped.

Description/symptom of problem: 

The problem spelled out  has three symptoms which is illustrated with the following scenario.

All of the servers in the server group are started.
The client is then started and through JNDI finds the home for some EJB.
The client then uses the home to access some object.  
Some server is stopped.

The different symptoms occur based on when the server is stopped and which server is stopped.

Symptoms
No error messages and fail over is successful
    This symptom is experienced when any one of the servers is stopped after the client has accessed the object.
One or no instances of the messages that you describe and fail over is successful
    This symptom is experienced when the last server to start is not the one that is stopped.
A communication error is reported to the client (ie no fail over) 
    This symptom is experienced when the last server to start is the one that is stopped and the server is stopped before the client uses the object. 

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 <jarfile name>

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/<APAR#> 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/<APAR#>).

2) Shutdown WebSphere

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

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.



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

none