Use this task to start the lightweight memory leak detection
using the Performance and Diagnostic Advisor.
Before you begin
If you have a memory leak and want to confirm the leak, or
you want to automatically generate heap dumps on Java virtual machines (JVM) in WebSphere® Application Server,
consider changing your minimum and maximum heap sizes to be equal.
This change provides the memory leak detection more time for reliable
diagnosis.
About this task
To start the lightweight memory leak detection using the
Performance and Diagnostic Advisor, perform
the following steps in the administrative console:
Procedure
- Click Servers > Application servers in the administrative
console navigation tree.
- Click server_name > Performance and Diagnostic Advisor Configuration.
- Click the Runtime tab.
- Enable the Performance and Diagnostic Advisor Framework.
- Click OK.
- From the Runtime or Configuration tab of Performance and Diagnostic Advisor Framework,
click Performance and Diagnostic Advice configuration.
- Start the memory leak detection advice and stop any other
unwanted advice.
Results
The memory leak detection advice is started.
Important: To achieve the best results for performance tuning, start the Performance and Diagnostic Advisor when a
stable production level load is running.
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.
What to do next
You can monitor any notifications of memory leaks by checking
the
SystemOut.log file or Runtime Messages. For more information,
see the
Viewing the Performance and Diagnostic Advisor recommendations topic.