Dynamic classes/classloaders may not be using the appropriate containing
classloader, resulting in permgen leaks
----------------------------------------------------------------------------------------------------------------
Key: JRUBY-1524
URL: http://jira.codehaus.org/browse/JRUBY-1524
Project: JRuby
Issue Type: Bug
Components: Miscellaneous
Reporter: Charles Oliver Nutter
Assignee: Thomas E Enebo
Priority: Blocker
Fix For: JRuby 1.0.3, JRuby 1.1
A team at Sun has run into a situation when redeploying their JRuby on
Rails-based application where permgen eventually fills up. Because a
well-behaved webapp should only be loading classes and constructing
classloaders under the webapp's classloader, allowing the entire classloader
subtree to be disposed when the webapp undeploys or redeploys, this most likely
points to JRuby misbehaving. We need to audit all locations where we construct
classloaders or load classes at runtime to ensure they are all happening under
the appropriate containing classloader, rather than under a system classloader
potentially outside the current application.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
