Enable automated heap dump generation
Use this task to enable automated heap dump generation. This function is not supported when using a Sun JVM which includes WAS running on HP-UX and Solaris operating systems. we need to research taking heap dumps on Sun JVMs or call IBM Support.
Although heap dumps are only generated in response to a detected memory leak, understand that generating heap dumps can have a severe performance impact on WAS for several minutes.
The automated heap dump generation support, which is available only on IBM Software Development Kit and analyzes memory leak problems on AIX, Linux, and Windows operating systems.
Manually generating heap dumps at appropriate times might be difficult. To help you analyze memory leak problems when memory leak detection occurs, some automated heap dump generation support is available. This functionality is available only for IBM Software Development Kit on AIX, Linux, and Windows operating systems.
Most memory leak analysis tools perform some forms of difference evaluation on two heap dumps. Upon detection of a suspicious memory situation, two heap dumps are automatically generated at appropriate times. The general idea is to take an initial heap dump as soon as problem detection occurs. Monitor the memory usage and take another heap dump when you determine that enough memory is leaked, so that we can compare the heap dumps to find the source of the leak.
To help you analyze memory leak problems when memory leak detection occurs, some automated heap dump generation support is available.
To enable automated heap dump generation support, perform the following steps in the admin console:
- Click Servers > Application servers in the admin console navigation tree.
- Click myserver >Performance and Diagnostic Advisor Configuration.
- Click the Runtime tab.
- Select the Enable automatic heap dump collection check box.
- Click OK.
Results
The automated heap dump generation support is enabled.Important: To preserve disk space, the Performance and Diagnostic Advisor does not take heap dumps if more than 10 heap dumps already exist in the WAS home directory. Depending on the size of the heap and the workload on the appserver, taking a heap dump might be quite expensive and might temporarily affect system performance.
The automatic heap dump generation process dynamically reacts to various memory conditions and generates dumps only when it is needed. When the heap memory is too low, the heap dumps cannot be taken or the heap dump generation cannot be complete.
Next steps
We can monitor any notifications of memory leaks by checking SystemOut.log or Runtime Messages. For more information, see the View the Performance and Diagnostic Advisor recommendations topic. If a memory leak is detected and you want to find the heap dump, refer to the Locating and analyzing heap dumps topic.
Generating heap dumps manually
Locating and analyzing heap dumps
Related information
Starting the lightweight memory leak detection