Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Jetty/Howto/Prevent Memory Leaks

< Jetty‎ | Howto
Revision as of 23:37, 9 August 2012 by Unnamed Poltroon (Talk) (New page: {{Jetty Howto | introduction = Well, the most obvious cause of this is memory leaks in your application :) But, if you've thoroughly investigated using tools like jconsole, yourkit, jprofi...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)



Introduction

Well, the most obvious cause of this is memory leaks in your application :) But, if you've thoroughly investigated using tools like jconsole, yourkit, jprofiler or any of the other profiling and analysis tools out there and you can eliminate your code as the source of the problem, read on.

Preventing WebApp Classloader Pinning

There's a class of memory leak problems that are caused by code keeping static references to a webapp classloader. As the webapp is undeployed and redeployed, the static reference lives on, meaning that the webapp classloader cannot be garbage collected, and eventually leading to permgen exhaustion.


JSP bugs

JVM bugs

Back to the top