eFix (APAR): pq54436 

Status:      Efix 

For Release: WebSphere 4.0.2

For Edition: WebSphere AE, AEs

For ContainerTypes: AEServer, AEsServer

For Operating System: All

Supersedes eFixes: None

CMVC defect: PQ54436 

Byte size of APAR: 879,975

Date: 2/8/02

Abstract: Multi-node domain with one node disconnected, then the HEALTHY node will recycled.

Description/symptom of problem: 

The problems seen with the system management topology were caused by several timing issues. 
With the second admin node down, the Solaris hardware will wait for up to 4.5 minutes, 
depending on the configuration, before it returns from creating a socket. This time was 
multiplied by the fact that the ORB does retries to compensate for the file system handles 
not being available. The retries have been removed to lessen the amount of time that the wait
on the socket creation. The extended wait caused the transaction that is used by the system 
management topology to fail. Without the retries the ORB returns the failure to connect 
before the transaction times out.

A second problem occurred during this time out because of a synchronization block that was 
waiting on the socket creation. This sync block was reduced to include only the connection 
table update. This allows a second connection to be established during the wait period. 
This caused the topology to not show any other servers that were running with the admin 
node that was up.

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
   (The zip/tar file will be created by WebSphere L2 Support.  It will contain the
    the efix jar file, the readme.txt file, and any other standard information required
    by IBM)

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:
------------------------------------------------------------------