You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2012/05/29 15:15:44 UTC

[Bug 53081] WebappClassLoader causes java.lang.OutOfMemoryError in findResourceInternal()

https://issues.apache.org/bugzilla/show_bug.cgi?id=53081

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Mark Thomas <ma...@apache.org> ---
As far as I can tell, the full resource has always been cached going back to
the original implementation of the WebappClassLoader back in Tomcat 4.

This has been fixed in trunk and 7.0.x so the only things cached are a) classes
(only temporarily until they are defined) and b) properties files needing
encoding conversion. Note that the class loading code has been fragile in the
past and it is possible that the fix may introduce a regression. If this is the
case, it is likely the fix will be reverted and the advice will then be "don't
load large static resources this way".

Assuming no problems emerge during testing, the fix will be in 7.0.28 onwards.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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