Step 4. Resource leak?

Is there a resource leak?

How do I know?
  1. In the left Navigation pane, go to (for example) Metric Browser > Application Infrastructure Performance > TierName > Individual Nodes > NodeName > JMX > JDBC Connection Pools > PoolName.
  2. Add the Active Connections and Maximum Connection metrics to the graph.
  3. Repeat as needed for various pools your application is using.
    If connections are not being released (use is trending upward), the answer to the question in Step 7 is Yes. Otherwise, the answer is No.
    • Yes – To determine where in your code resources are being created but not being released as needed, take a few thread dumps using standard commands on the problematic node. You can also create a diagnostic action within Splunk AppDynamics to create a thread dump; see Thread Dump Actions in Diagnostic Actions.
    • No – Restart the JVM. If none of the above diagnostic steps addressed your issue, it's possible you're simply seeing a one-time unusual circumstance, which restarting the JVM can resolve.