Manual heap dumps are captured at your discretion at any time during
the profiling run. Capture a heap dump after application warm-up (during which
all the classes of interest to you are loaded and initialized), and another
heap dump after exercising transactions that you suspect of leaking memory.
To collect data using manual heap dumps:
- In the Profiling page (Overview subpage) of the Profile dialog
box, select the Memory Leak Analysis - Manual heap dumps profiling
set.
- If you want to adjust the threshold for reporting leak candidates,
perform the following steps. The default value is 20. Decreasing
the threshold value means that you display more potential leaks.
- Click Edit, then Next,
to open the Automatic Leak Detection page.
- Set the threshold to a value between 1 and 99.
- Click Finish.
- Click Profile to start your application.
- Click the Capture Heap Dump button
to
capture your first heap dump after your application has warmed up. Heap dumps
are added in the Profiling Monitor as profiling resources.
- Exercise your application and click the Capture Heap Dump button
again to capture a second heap dump. You can now terminate or detach
your application, but you can also leave it running and capture additional
heap dumps to investigate other parts of your application.