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

ASF GitHub Bot commented on WW-5035:
------------------------------------

yasserzamani commented on pull request #361: Proposed WW-5035 enhancement:
URL: https://github.com/apache/struts/pull/361
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Provide mechanism to clear OgnlUtil caches
> ------------------------------------------
>
>                 Key: WW-5035
>                 URL: https://issues.apache.org/jira/browse/WW-5035
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core
>         Environment: All
>            Reporter: James Chaplin
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.5.21
>
>
> Hello Apache Struts Team.
> This Jira proposes to provide some cache-clearing methods for the OgnlUtil 
> class, as well as methods to check the current cache element count.
> These methods will allow applications to clear the OgnlUtil expression cache 
> and BeanInfo cache when necessary (using application-specific usage profile).
> Currently the only OgnlUtil cache control available to applications is to 
> enable/disable the OgnlUtil expressionCache 
> ({{struts.ognl.enableExpressionCache flag}}). 
> Using the new methods applications that have resource (memory) leak issues 
> with the caches may be able to use the caches to gain some performance 
> benefits, while periodically clearing them to recover memory resources.  
> Application developers can determine how frequently (e.g. hourly, daily) such 
> cache clearing is needed.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to