Fix (APAR):  PQ71967

Status:  Fix

Release:  4.0.5,4.0.4,4.0.3,4.0.2

Operating System:  All

Supersedes Fixes:  stand-alone fix

CMVC Defect:  PQ71967

Byte size of APAR:  1067984

Date: 2003-12-11

Abstract:  Admin clients process hang or does not terminate when issued start/stop commands.

Description/symptom of problem:  
                                                   
The issue fixed on this defect does not address the GUI status bar directly.
What is addressed here is that when the clients (wscp,GUI,xmlconfig) issues a request to 
adminserver to start/stop appserver, the clients are expecting a notification back from adminserver that
the operation had been completed.  Before the notification is received by the client, the client thread is
blocked and waiting.  The problem is there is a timeout implemented but it's not working properly.
If for whatever reasons the notification was not received, the timeout does not occur, resulting with indefinite
hang on the clients.  Customer will often see the WSCP, XMLconfig process remains even after the operation had 
completed.







Directions to apply fix:  

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) Restart WebSphere

6) 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 fix:  

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

Follow the instructions for applying an fix.  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:  
------------------------------------------------------------------

*** IMPORTANT NOTE ****

This is a stand-alone fix. It provides temporary resolution to the target problem only.
This fix will be incorporated into upcoming System Management Cumulative fix.
Customer should apply the updated System Management Cumulative fix to avoid versioning
conflicts between stand-alone fixes.

This fix uses the most recent code base (on top of WAS4.0.5), it passed ad hoc testing
on earlier versions, but customer may need to apply the latest SM cumulative fix or PTF
prior to apply this fix to update any dependent classes.

This fix jar was packaged using JDK 1.3.1 that shipped with WAS4.0.5.