Fix (APAR):  PK03275

Status:  Fix

Release:  5.1.1.3,5.1.1.2,5.1.1.1,5.1.1,5.1.0.6,5.1.0.5,5.1.0.4,5.1.0.3,5.1.0.2,5.1.0.1,5.1.0

Operating System:  All

Supersedes Fixes:  

CMVC Defect:  PK03275

Byte size of APAR:  24824

Date: 2005-04-08

Abstract:  Websphere's systemout.log file contains too many PMI warning messages (PMI0002, PMI0016, PMI0018 and PMI0024).

Description/symptom of problem:  In some instances external performance monitoring applications accessing Websphere's performance infrastructure precipitate a large number of warning messages (PMI0002, PMI0016, PMI0018 and PMI0024) to be displayed in the system logs.  This patch will mask these messages so that they will only be displayed when the PMI component is being traced.

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

1) Create temporary "fix" directory to store the jar file:
             UNIX: /tmp/WebSphere/fix
          Windows: c:\temp\WebSphere\fix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Follow the Fix installation instructions that are packaged with the Fix Installer on how 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 A 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 Fix Installer on how to uninstall the Fix.

3) Restart WebSphere

Directions to re-apply fix:  1) Shutdown WebSphere

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere

Additional Information: