MustGather: 100% CPU Usage on Solaris platforms

Technote (FAQ)
Problem
MustGather for problems with the WebSphere® Application Server or other Java™ Virtual Machine (JVM™) experiencing 100% or unusually high CPU usage on Solaris™ platforms. Gathering this information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.
Solution
This documents outlines what is needed to troubleshoot a JVM that causes the CPU utilization to reach 100%, or an unusually high percentage, on a Solaris system.


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.

Follow the below instructions to setup the failing System for capturing required information:

  1. Follow instructions to Enable verbosegc for the failing application server.
  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, perform 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

Collect the following information when the application server process is experiencing the problem:

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

    ./wascpu.sh PID
  2. Collect the following files:

    • For V6.0 release:
      1. All files in <install_root>/profiles/<ProfileName>/logs/<ServerName> directory.
      2. A copy of server.xml located in <install_root>/profiles/<ProfileName>/config/cells/<CellName>/nodes/<NodeName>/servers/<ServerName>director
    • For all V5.0 and V5.1 releases:
      • Include all of the files from the <install_root>\logs\<ServerName>directory.
      • A copy of server.xml located at <install_root>\config\cells\<CellName>\nodes\<nodeName>\servers\<ServerName> directory
    • For all V3.5, and V4.0 releases:
      • Include all of the files from the <install_root>\logs directory.
      • 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 send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the100% CPU Usage component, search the WebSphere Application Server support site.

Related information
How to enable verbosegc in WebSphere

Determining which Java thread is consuming CPU

lsof download link

Steps to Getting Support

MustGather: Readme First

Troubleshooting Guide












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, 100% CPU Usage
Operating system(s): Solaris
Software version: 3.5, 4.0, 5.0, 5.1, 6.0
Software edition: Advanced, Base, Express, Network Deployment, Single Server
Reference #: 1115625
IBM Group: Software Group
Modified date: 2004-12-09