MustGather: Out of Memory Errors on Windows, part 1

Technote (FAQ)
Problem
MustGather for problems with the WebSphere® Application Server (all versions) Out of Memory component on a Microsoft® Windows® platform. Gathering this information before calling IBM® support helps familiarize you with the troubleshooting process and saves you time.
Solution
Two conditions can cause a java.lang.OutOfMemoryError:
  • The Java™ Virtual Machine (JVM™) might run out of Java heap space to allocate a Java object.
  • The JVM might not be able to allocate the native memory needed for all threads to execute.

If you already contacted support, continue gathering the MustGather information for the applicable component. Otherwise, click on the following link: MustGather: Read First for all WebSphere Application Server Products.

Out of Memory Errors (Windows) specific MustGather information

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

  1. Follow instructions for enabling verbosegc in WebSphere Application Server
  2. Stop the Application Server.
  3. Clear all Application Server log files before starting test.
  4. Restart the Application Server.
  5. Wait for your problem to re-occur.
  6. Collect the following:
    • For release V6.0:
      1. All files in install_root\profiles\profile_name\logs\server_name directory.
      2. All files in install_root\profiles\profile_name\logs\ffdc directory.
      3. A copy of server.xml located in install_root\profiles\profile_name\config\cells\cell_name\nodes\node_name\servers\server_namedirectory
    • For releases V5.0 and V5.1:
      1. Include all of the files from the install_root\logs\server_name directory.
      2. All files in install_root/logs/ffdc directory
      3. A copy of server.xml located at install_root\config\cells\cell_name\nodes\node_name\servers\server_name directory
    • For releases V3.5 and V4.0:
      1. Include all of the files from the install_root\logs directory.
      2. A copy of XMLExport for the server configuration
    • For all releases:
      • All heapdump*.* and javacore*.* files if any were generated by the Out Of Memory condition.
      • Note: For all versions, If you have configured the Application Server to write logs into a different location, send them accordingly.

  7. Determine if source for leak is the Java heap or native memory:
    1. If available memory does NOT drop, follow instructions in
      MustGather: Out of Memory Errors on Windows, Part 2a - Native Leak

    2. If available memory listed in heap drops over time, follow instructions in
      MustGather: Out of Memory errors on Windows, Part 2b - heap leak

  8. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the Out of Memory component, search the WebSphere Application Server Support site for out of memory or java.lang.OutOfMemoryError.

Related information
How to enable verbosegc in WebSphere

Submitting information to IBM support

Steps to getting support

MustGather: Readme first

Troubleshooting guide












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Out of Memory
Operating system(s): Windows
Software version: 3.5, 4.0, 5.0, 5.1, 6.0
Software edition: Advanced, Base, Express, Network Deployment, Single Server, Standard
Reference #: 1055371
IBM Group: Software Group
Modified date: 2004-12-15