Two conditions can cause a java.lang.OutOfMemoryError
error:
- The Java™ Virtual Machine (JVM™) runs out of Java heap space to
allocate a Java object.
- The JVM is not be able to allocate the native memory that it needs to
create or execute threads.
If you have already contacted support, continue to the component-specific
MustGather information. Otherwise, click the following link: MustGather: Read First for all WebSphere Application
Server Products.
Follow the below instructions to setup the failing system for capturing
required information:
- Follow the instructions on How to enable verbosegc on WebSphere Application
Server before recreating the problem.
- Restart the Application Server.
- Run the Solaris_ps.sh and Solaris_pmap.sh
scripts (see attached scripts). Pass the script the sample period (time in
seconds). This tells the script how often to take snapshots.
For example, if the problem can be reproduced in 1 hour, pass the script
300 so that the documentation is collected every 5 minutes. For a problem
that takes 2 days to reproduce, 1200 is a good sample period.
- Wait for problem to re-occur.
- Stop the Application Server and the script.
- Collect the following:
- For release V6.0:
- All files in
install_root/profiles/profile_name/logs/server_name
directory.
- All files in
install_root/profiles/profile_name/logs/ffdc
directory.
- A copy of server.xml located in
install_root/profiles/profile_name/config/cells/cell_name/nodes/node_name/servers/server_name
directory
- For releases V5.0 and V5.1:
- Include all of the files from the
install_root/logs/server_name directory.
- All files in
install_root/logs/ffdc
directory.
- 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:
- Include all of the files from the
install_root/logs directory.
- A copy of XMLExport for the server configuration
- For all releases:
- All jtc*.log files created from running the
script in Step 4.
- Note: For all versions, If you have configured the
Application Server to write logs into a different location, send them
accordingly.
- Important: If the data collected in this document
indicates a leak in the Java heap, proceed to the technote under Related
Information below.
- 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.
|