Fix (APAR):  PH24552

Status:  Fix

Release:  8.5.5.17

Operating System:  Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  348562

Date: 2020-05-19

Abstract:  PI89036 causes native_stdout to fill up with repeating debug timestamps

Description/symptom of problem:  
PH24552 resolves the following problem:

ERROR DESCRIPTION:
WAS ND 9.0.5.3 and 8.5.5.17 on Windows                                       
                                                                
After updating to WAS 9.0.5.3 or 8.5.5.17, PI89036 results in continual     
debug timestamps generated to native_stdout:                    
                                                                
ProcessCPU                                                      
Java_com_ibm_ws_xd_pmi_processcpu_ProcessCPU_nativeEnableDebugMode ENTER                                                        
ProcessCPU                                                      
Java_com_ibm_ws_xd_pmi_processcpu_ProcessCPU_nativeEnableDebugMode EXIT                                                         
                                                                
followed by a series of timestamps every 15 seconds:            
                                                                
[04/16/20  14:39:06]                                            
[04/16/20  14:39:06]                                            
...                                                             
[04/16/20  14:39:21]                                            
[04/16/20  14:39:21]                                            
...                                                             

LOCAL FIX:
none                                                            

PROBLEM SUMMARY:
Over a period of time, native_stdout.log on Windows fills up with
repeating debug timestamps when PMI is invoked to collect CPU
statistics. This was caused due to a fix for PI89036 which failed
to check for debug mode prior to writing out some timestamps in
the log file.

USERS AFFECTED:
All users of IBM WebSphere Application Server

PROBLEM DESCRIPTION:
native_stdout.log on Windows fills up with repeating debug timestamps 
when PMI is invoked to collect CPU statistics

RECOMMENDATION:
None

PROBLEM CONCLUSION:
The code was updated to check for debug mode prior to writing ou
timestamps to native_stdout.log.                                
                                                                
The fix for this APAR is targeted for inclusion in fix packs    
8.5.5.18 and 9.0.5.4. For more information, see 'Recommended    
Updates for WebSphere Application Server':                      
http://www.ibm.com/support/docview.wss?uid=swg27004980   


Directions to apply fix:  
Fix applies to Editions:
Release 8.5
__ Application Server (Express or BASE)
_X_ Network Deployment (ND)
__ Liberty Core
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information:  The Windows machine needs to be restarted at OS  level following the fix installation.