eFix (APAR): PQ67353
Status:      efix

Release: WebSphere 4.0.4

Supersedes eFixes: NONE - this eFix is NOT cumulative.

CMVC defect: PQ67353

Byte size of APAR:   1061140 bytes

Date: 28Oct02

Title: admin service exits w/o explanation

Error Description:

    On Windows platforms, when the admin service launches the admin
    server, the admin service waits 480 seconds for the admin
    server to  notify it that the admin server (and any application
    servers that the admin server was configured to start) are
    fully ready.
    
    In some cases, where the application servers may take a long
    time to start, the admin service would timeout and exit without
    explanation.  The admin server and any application servers
    would be left running and  function without problem but, if the
    admin server should ever  terminate, there would be no admin
    service running to restart it.
    
    This APAR corrects that problem by setting the default timeout for 
    this period to be INFINITE (i.e., no timeout).  This APAR also
    introduces two additional properties that the user can add to
    admin.config to modify some of the admin service behavior. For 
    additional information on these properties, see #5 below

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 PQ67353_eFix.jar

5)  >>>PLEASE NOTE: <<<

This PMR exposes two new properties that can be added to admin.config
to modify the behavior of the admin service for WebSphere on Windows 
platforms. 

These properties are:

    1)  com.ibm.ejs.sm.adminService.verboseLogging
    
        If this property is set to a non-zero value as in:
        
           com.ibm.ejs.sm.adminService.verboseLogging=1
        
        then the admin service will produce additional entries in the 
        Windows Application Event Log.
    
    2)  com.ibm.ejs.sm.adminServce.waitForTimeOut
    
        This property sets the number of seconds that the admin service
        will wait for the admin server to notify it that it (the admin
        server) and  all app servers that it started have completed
        their startup.
        
        The default value for this property is 0 which means that the
        admin service will not timeout waiting for notification from
        the admin  server.  
        
        UNDER NORMAL CIRCUMSTANCES THE USER SHOULD NOT NEED TO BE SET
        THIS PROPERTY FROM ITS DEFAULT VALUE.

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

This is NOT a cumulative efix. I