You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2007/08/20 18:33:30 UTC
[jira] Commented: (EL-1) [el] Memory Leak: EL Cache entries never
removed.
[ https://issues.apache.org/jira/browse/EL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521141 ]
Henri Yandell commented on EL-1:
--------------------------------
Need to check JSTL to see what bug reports that has in this area.
> [el] Memory Leak: EL Cache entries never removed.
> -------------------------------------------------
>
> Key: EL-1
> URL: https://issues.apache.org/jira/browse/EL-1
> Project: Commons EL
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Operating System: All
> Platform: All
> Reporter: Bill Alexander
>
> This bug refers to the two caches on ExpressionEvaluatorImpl,
> sCachedExpressionStrings, but primarily sCachedExpectedTypes.
> Here is a use case to illustrate the problem. A web application typically
> creates 1,000 different objects of classes it defines using the EL language, and
> PropertyEditor's. A Tomcat instance is run with 5 of these web applications.
> Each time one of them is reloaded, a new classloader is created for the web
> application, so a new set of 1,000 objects is created in the cache. The old
> objects, and objects they point to (e.g. class and classloader objects), are
> never garbage collected. The only way to recover the associated memory is to
> stop and restart Tomcat.
> There are many possible solutions. A simple one would be to age instances out
> of the caches after a fixed period of time (say one hour). It would be nice if
> whatever cache controls are provided are configurable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.