This blog promotes knowledge sharing through experience and collaboration. For more product information, visit our WebSphere Commerce CSE page. For easier navigation, utilize the Categories to find posts that match your interest.
Being ready for OutOfMemory errors
OutOfMemory is among the most common errors that lead to outages and performance degradation. In this post I share tips for how to configure the JVMs to ensure all the information required for debugging is generated the first time, so there is no need to wait for a next occurrence.
This post is written for the IBM JDK 1.6 used with WebSphere Commerce v7.0 on Windows, Linux and AIX for Heap memory issues (not native).
WebSphere MustGathers for OutOfMemory
The following MustGather lists the files that will be required to troubleshoot an OutOfMemory exception (heap): MustGather: Out of Memory errors with WebSphere Application Server on AIX, Linux, or Windows
Become familiar with all the files listed. Ensure the required configurations are in place, and the files are preserved after an incident.
All except native_stderr.log are created in the profile directory.
Configuring for OutOfMemory errors
Javacores and heapdumps are automatically generated. Verbose Garbage collection, and full core generation require additional configurations:
Analyzing the data
There are multiple tools and techniques for resolving OutOfMemory errors. See OOM tagged posts in this site. This presentation also provides a good introduction into the topic: Webcast replay: Troubleshooting Out-of-Memory Errors in WebSphere Commerce.