Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change 
notification.

The "MemoryLeakProtection" page has been changed by KonstantinKolinko:
http://wiki.apache.org/tomcat/MemoryLeakProtection?action=diff&rev1=15&rev2=16

Comment:
Add reference to BZ 53936 that proposes a workaround for classloader leaks 
caused by long-lived Exceptions

  Related issues
   * <<Anchor(49159)>>[[https://issues.apache.org/bugzilla/show_bug.cgi?id= 
49159|49159]] - Improve ThreadLocal memory leak clean-up
   * [[http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4957990|Sun bug 
4957990]] - In some cases the Server JVM fails to collect classloaders. 
According to [[http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4957990|this 
page]] it should have been fixed with java 6u16 but actually it was not. It 
seems to be fixed with 6u21 (documented 
[[http://download.java.net/jdk6/6u21/promoted/b03/changes/JDK6u21.list.html|here]]
 and verified by the author of this wiki page).
-  * [[http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6916498|Sun bug 
6916498]] - An exception can keep a classloader in memory if the stack trace 
that was recorded when it was created contains a reference to one of its 
classes. Some fixes have been made in tomcat (see 
[[https://issues.apache.org/bugzilla/show_bug.cgi?id=50460|BZ 50460]]), but 
some library or JRE code may still create a leak that is undetected by tools 
because of this JVM bug.
+  * [[http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6916498|Sun bug 
6916498]] - An exception can keep a classloader in memory if the stack trace 
that was recorded when it was created contains a reference to one of its 
classes. Fixes were done in Tomcat for its own classes that had this issue (see 
[[https://issues.apache.org/bugzilla/show_bug.cgi?id=50460|BZ 50460]]), but 
some library or JRE code may still create a leak that is undetected by tools 
because of this JVM bug. See also 
[[https://issues.apache.org/bugzilla/show_bug.cgi?id=53936|BZ 53936]] for a 
workaround that you can implement if you are unable to fix a buggy library.
  
  ----
  [[CategoryFAQ]]

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to