If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.


100% CPU Usage specific MustGather information
Follow these instructions to set up the failing System for capturing required information:

1. Enable verbosegc for the failing application server. This is necessary for debugging High CPU issues and does not have significant impact on performance.
   
   
2. Clear all application server log files before starting test. You may have to stop the Application Server to delete the files and then start them.
   
   
3. After starting the Application Server, run the following netstat and vmstat commands to capture typical system CPU and connection activity:
   
   

   % netstat -an > netstat_normal.out % vmstat 5 12 > vmstat_normal.out

1. Execute the following script (see attached) where PID is the process ID of the Java process causing high CPU.
   
   

   ./wascpu.sh  PID

2. Collect the following files:
   
   
   • For WebSphere V6.0:
     • All files in the following directory:
       
       

       install_root/profiles/profile_name/logs/server_name

     • A copy of server.xml located in the following directory:
       
       

       install_root/profiles/profile_name/config/cells/ cell_name/nodes/node_name/servers/server_name

   • For WebSphere V5.0 and V5.1:
     • All files in the following directory:
       
       

       install_root\logs\server_name

     • A copy of server.xml located at the following directory:
       
       

       install_root\config\cells\cell_name\nodes\ node_name\servers\server_name

   • For WebSphere V3.5, and V4.0:
     • All files in the following directory:
       
       

       install_root\logs

     • A copy of XMLExport for the server configuration.
       
       
   • If the Web server is remote, send the trace.log.Web_server_name.date (V3.5), native.log (V4.0), or http_plugin.log (V5.0 and V6.0) file from the Web server system.
     
     
   • All of the *.out files created by the wascpu.sh script.
     
     
   • netstat_normal.out and vmstat_normal.out (if possible).
     
     
3. Follow instructions to Submitting Diagnostic Information to IBM Technical Support for Problem Determination.