Step 3. Memory leak?

Is there a memory leak?

How do I know?
  1. From the list of nodes displayed in the previous step (when you were checking for Garbage Collecting activity), double-click a node that is experiencing significant GC activity.
  2. Click the Memory tab, then scroll down to display the Memory Pool graphs at the bottom of the panel.
  3. Double-click theOld Gen memory poolschart.
    If memory is not being released (use is trending upward), the answer to this question is Yes. Otherwise, the answer is No.
    • Yes – Use various Splunk AppDynamics features to track down the leak. One useful tool for diagnosing a memory leak is object instance tracking, which lets you track objects you are creating and determine why they aren't being released as needed. Using object instance tracking, you can pinpoint exactly where in the code the leak is occurring. For instructions on configuring object instance tracking, as well as links to other tools for finding and fixing memory leaks, see Need more help?.
    • No – Increase the size of the JVM. If there is significant GC activity but there isn't a memory leak, then you probably aren't configuring a large enough heap size for the activities the code is performing. Increasing the available memory should resolve your problem.

    Whether you answered Yes or No, you have isolated the problem.