MustGather: Native Memory Issues on Linux

Technote (troubleshooting)


Problem(Abstract)

MustGather for native memory problems with the WebSphere Application Server on Linux. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Cause

A native OutOfMemory condition occurs when the Java™ virtual machine is unable to allocate native memory.

Resolving the problem

If you have already contacted IBM WebSphere technical support, continue to the component-specific MustGather information recommended by that analyst. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.

Out of Memory (native) specific MustGather information

  1. Enable verbosegc. For more details, see Enabling verbosegc in WebSphere Application Server.
  2. Stop the WebSphere Application Server.
  3. Clear all Application Server log files.
  4. Restart the Application Server.
  5. Recreate the Out of Memory condition, or wait for the condition to reoccur.
  6. Collect the following logs:
    • All files located in the following directory:
      profile_root/logs/server_name/*.
    • Collect the heapdump*.* , javacore*.*, and server.xml for the OutOfMemoryError on the affected server.
    • 'ulimit -a' output for the environment
  7. Generate a system core and collect the system libraries.
    For more details, see Generating a core file and malloc trace on Linux.
  8. Package and compress these logs into a single file. Follow the instructions for Submitting data to IBM Support to send in the preceding diagnostic information.




Monitoring Memory Usage For All Processes
If requested by IBM support, please run the linux-psscript.sh script while recreating the issue. The linux-psscript.sh script is located at the bottom of this page.

Run as follows:
linux-psscript.sh [-f filename] [-i interval]

Where:
<filename> is the output filename file
<interval> is the time in seconds between each iteration

The default values for these options are usually sufficient. IBM Support will direct you if parameters are required.



Monitoring Memory Usage For a Single Process
If requested by IBM support, please run the linux-asmemory.sh script while recreating the issue. The linux-asmemory.sh script is located at the bottom of this page.

Run as follows:
linux-asmemory.sh -p pid [-f filename] [-i interval]

Where:
<pid> is the process id to be profiled (Mandatory)
<filename> is the output filename file
<interval> is the time in seconds between each iteration

The default values for these options are usually sufficient. IBM Support will direct you if parameters are required.




Malloc Trace
If requested by IBM support, please collect a Malloc Trace. Instructions for collecting a Malloc Trace can be found at: Generating a core file and malloc trace on Linux.

Related information

MustGather: Out of Memory errors on AIX Linux or Window
Submitting information to IBM support
Steps for getting support
MustGather: Readme first
Troubleshooting guide
Enabling verbose garbage collection (verbosegc)

linux-psscript.shlinux-asmemory.sh


Cross reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express General Linux 7.0, 6.1, 6.0.2, 6.0.1, 6.0

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server
Out of Memory

Software version:

6.0, 6.1, 7.0, 8.0, 8.5

Operating system(s):

Linux

Software edition:

Advanced, Base, Express, Network Deployment, Single Server, Standard

Reference #:

1138462

Modified date:

2010-07-29

Translate my page

Machine Translation

Content navigation