commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (EL-1) [el] Memory Leak: EL Cache entries never removed.
Date Tue, 04 Sep 2007 13:12:44 GMT

    [ https://issues.apache.org/jira/browse/EL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524715
] 

Henri Yandell commented on EL-1:
--------------------------------

Looking in JSTL (Jakarta Taglibs Standard), this has already been reported there:

http://issues.apache.org/bugzilla/show_bug.cgi?id=31789

Having messed with this and a couple of other caching issues, my thought was not to change
things around as I didn't want to make sure a large change and because I didn't think that
cached EL expressions would lead to that much memory usage. That's mostly because I don't
redeploy web applications a lot.

> [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.


Mime
View raw message