Fix (APAR):  WAS_Classloader_07-18-2003_5.0.1-5.0.0_cumulative_Fix

Status:  Fix

Release:  5.0.1,5.0.0

Operating System:  All

Supersedes Fixes:  PQ72658, WAS_Classloader_04-08-2003_5.0.0_cumulative_Fix

CMVC Defect:  PQ75469

Byte size of APAR:  33921

Date: 2003-07-18

Abstract:  WebSphere 5.0.1-5.0.0 Classloader 07-18-2003 Cumulative Fix

Description/symptom of problem:  This is a cumulative Runtime and Classloader
   fix set, correcting the following problems:

   Addressed customer problems:
      
      - PQ72658
        Class-Path entries in jar files configured as shared libraries are not
        being added to the class loader, resulting in "class not found" errors.
        For example, if a.jar is configured as part of a shared library, and
        the manifest of a.jar lists a Class-Path dependency on b.jar, then
        classes in b.jar may not be found at runtime.
        
      - PQ73332
        ConcurrentModificationException in ReloadableClassLoader.
        In environments where dynamic class reloading is enabled (e.g. the WSAD
        Unit Test Environment), intermittent exceptions of type
        java.util.ConcurrentModificationException may be experienced.
        
      - PQ75469
        If a shared library is defined as a directory only, the jar files in
        the directory may not added to the classloader, resulting in
        "class not found" errors.  For 5.0.x, this occurs with server
        associated shared libraries.  For 5.0.2, this also occurs with
        application associated shared libraries.
        
      - Additional fixes
        ReloadTaskTimer not cancelled.  As applications are stopped and
        restarted, the corresponding timer task that detects class file 
        changes is not cancelled.
        
   All of these fixes, with the exception of PQ75469, are in 5.0.2.  The
   PQ75469 fix will be available in the next 5.0.2 Service Pack.

Directions to apply fix:  NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL AN FIX.
       The Fix Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/support/index.html

1) Download the cumulative fix set file in binary.

2) Create temporary "fix" directory to store the jar file:
             AIX, LINUX, UNIX: /tmp/WebSphere/fixrepos
                      Windows: c:\temp\WebSphere\fixrepos

3) Copy jar/tar/zip file to the directory created above.

4) If the fix was downloaded as a zip or tar file, please extract such that the 
   jar file is in the fixrepos directory.

3) Shutdown WebSphere

4) Follow the fix installation instructions that are packaged with the Update
   Installer to install the Fix.

5) Restart WebSphere

6) The temp directory may be removed.

Directions to remove fix:  NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN FIX UNLESS
     ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be
          removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere

2) Follow the instructions that are packaged with the Update Installer to uninstall the Fix.

3) Restart WebSphere

Directions to re-apply fix:  1) Follow the instructions for uninstalling a fix.

2) Follow the instructions for installing a fix.

Additional Information:  To list installed fixes:

Change directory to: %WAS_HOME%\bin
        
On Windows NT systems:
  For a general list of fix activity:
   versioninfo -efixDetail
  or to print out a summary list of fixes installed
   versioninfo -efixDetail | c:\winnt\system32\find "ID"
   
On supported Unix systems:
  For a general list of fix activity:
   versioninfo -efixDetail
  or to print out a summary list of fixes installed
   versioninfo -efixDetail | grep "ID"