Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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 01:08, 10 August 2012 by Janb.intalio.com (Talk | contribs)



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, jvisualvm 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 can eventually lead to permgen exhaustion. There's a good discussion of this issue here: [1]

We provide a number of [http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/util/preventers/package-summary.html

Back to the top