[ http://issues.apache.org/jira/browse/JCR-619?page=comments#action_12446928 ] Thomas Mueller commented on JCR-619: ------------------------------------
Hi, I just made some more (long running) tests, and found some problems in the patch I submitted. The mechanism is working, but it shrinks the caches too quickly, and it prints too much log output (log.info instead of log.debug). I will fix those problems and submit a new patch. Sorry. Thomas > CacheManager (Memory Management in Jackrabbit) > ---------------------------------------------- > > Key: JCR-619 > URL: http://issues.apache.org/jira/browse/JCR-619 > Project: Jackrabbit > Issue Type: New Feature > Components: core > Affects Versions: 1.1 > Reporter: Thomas Mueller > Attachments: cacheManager.txt > > > Jackrabbit can run out of memory because the the combined size of the various > caches is not managed. The biggest problem (for me) is the combined size of > the o.a.j.core.state.MLRUItemStateCache caches. Each session seems to create > a few (?) of those caches, and each one is limited to 4 MB by default. > I have implemented a dynamic (cache-) memory management service that > distributes a fixed amount of memory dynamically to all those caches. > Here is the patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
