commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EL-1) [el] Memory Leak: EL Cache entries never removed.
Date Sun, 25 Sep 2016 15:12:20 GMT

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

Jarek Jarcec Cecho commented on EL-1:
-------------------------------------

Thanks for the follow up [~britter], appreciated! I'll certainly take a look into using Tomcat
EL instead.

> [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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message