Resolving Out of Memory Errors when running WPG on WebSphere Application Server 6.1
MichaelGlenn 1200004UQ7 Visits (10465)
So have you been experiencing any of those nasty Out of Memory error messages when running WebSphere Partner Gateway (WPG) on WebSphere Application Server 6.1. During this period I have dealt with a number of these issues and I thought I would share some useful links to help troubleshoot these error messages.
The first step in troubleshooting these Out of Memory error messages is to enable verbosegc on your WebSphere Admin Console. To activate the verbosegc trace, use the Java runtime option -verbose:gc. This value is set in WebSphere Application Server admin console:
Once the above has been set then you would want to shutdown your application server then either backup your existing logs in the <WPG
The verbosegc output would appear in native_stderr.log in the log subdirectory:
Once you have captured the native_stderr.log file it is time to analyze it. There is a tool available called IBM Pattern Modeling and Analysis Tool (PMAT) for IBM Java Garbage Collector. This tool can be downloaded from:
For more information on using this tool, see Webcast replay: How to analyze verbosegc trace with IBM Pattern Modeling and Analysis Tool for IBM Java Garbage Collector.
Based on the analysis from the PMAT tool you might need to increase your java heap sizes on the server in question.
Besides the PMAT tool there are other very useful tools to analyze heap dumps such as the IBM Heap Analyzer which helps to detect heap leaks and also the IBM Thread and Monitor Dump Analyzer for Java which is used to diagnose hang and thread issues. For more information on these tools, see the Webcast document mentioned previously Webcast replay: How to analyze verbosegc trace with IBM Pattern Modeling and Analysis Tool for IBM Java Garbage Collector.
I hope this information makes it easier to diagnose and troubleshoot those out of memory errors.