Fix (APAR):  PQ73967

Status:  Fix

Release:  4.0.5,4.0.4,4.0.3,4.0.2

Operating System:  All

Supersedes Fixes:  None.





CMVC Defect:  PQ73967

Byte size of APAR:  1071280

Date: 2003-05-19

Abstract:  Application Server ORB initializes with Request Timeout = 0

Description/symptom of problem:  
                                                   
In WebSphere V4.0x if the application server Object Request
Broker (ORB) request timeout setting is allowed to
180, the actual initialization of the application server ORB
uses a request timeout of 0 (unlimited wait). Using the
administration console, if you change the request timeout value
within the Object Request Broker properties to any value other
than 180, it is properly used by application server ORB
initialization.

Default ORB RequestTimeout is inconsistent between adminitration 
console (180) and what is actually being used by ORB (0).  
This fix corrects the inconsistency and 
ensures underlying default ORB RequestTimeout is 0 on the 
console if no value had been persisted.  For existing customers 
applying the fix, the timeout value of 180 would have persisted 
unless otherwise specified.  Future PTF releases would show 
the correct default value of 0 on the console unless otherwise 
specified.  






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

*** NOTE ****

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