[
https://issues.apache.org/jira/browse/JCR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465457
]
Jaka Jaksic commented on JCR-619:
---------------------------------
> private static final long MAX_MEMORY = 16 * 1024 * 1024;
If I understand the CacheManager source correctly, the maximum size for all
caches is hardcoded to 16 megabytes and there's no way to change that other
than by changing the source. Now, while this is still a lot better than having
no upper limit at all and risk running out of memory if you have many
workspaces, it would be nice if this as well as other CacheManager parameters
were configurable. It's just a waste running Jackrabbit on a server with
gigabytes of memory and only using 16 megs for cache...
> CacheManager (Memory Management in Jackrabbit)
> ----------------------------------------------
>
> Key: JCR-619
> URL: https://issues.apache.org/jira/browse/JCR-619
> Project: Jackrabbit
> Issue Type: New Feature
> Components: core
> Reporter: Thomas Mueller
> Assigned To: Stefan Guggisberg
> Fix For: 1.2
>
> Attachments: cacheManager.txt, cacheManager2.txt, cacheManager5.txt,
> cacheManager6.txt, cacheManager7.txt, stack.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:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
