[
https://issues.apache.org/jira/browse/JCR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466330
]
Jaka Jaksic commented on JCR-619:
---------------------------------
I have created a really simple and straightforward patch
(jackrabbit-cachemanager-config.patch) which enables reaching the CacheManager
instance through RepositoryImpl object and setting all three of its memory
parameters. The memory parameters are no longer static constants, but instance
fields getting initial values from constants (so the default behavior doesn't
change).
Could this patch or something alike be included in a future release?
(It would also be nice to be able to set these parameters via configuration
files, but that should probably be implemented by someone close to the project.)
> 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.1
>
> Attachments: cacheManager.txt, cacheManager2.txt, cacheManager5.txt,
> cacheManager6.txt, cacheManager7.txt, jackrabbit-cachemanager-config.patch,
> 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
