From dev-return-18675-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Fri May 09 07:25:20 2008 Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 20103 invoked from network); 9 May 2008 07:25:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 May 2008 07:25:19 -0000 Received: (qmail 48939 invoked by uid 500); 9 May 2008 07:25:18 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 48873 invoked by uid 500); 9 May 2008 07:25:18 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 48855 invoked by uid 99); 9 May 2008 07:25:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 May 2008 00:25:18 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 May 2008 07:24:41 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id AE8B5234C112 for ; Fri, 9 May 2008 00:24:55 -0700 (PDT) Message-ID: <1045723996.1210317895713.JavaMail.jira@brutus> Date: Fri, 9 May 2008 00:24:55 -0700 (PDT) From: "Thomas Mueller (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-619) CacheManager (Memory Management in Jackrabbit) In-Reply-To: <6602807.1162551976602.JavaMail.root@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595488#action_12595488 ] Thomas Mueller commented on JCR-619: ------------------------------------ Hi, > Is it possible to use the Caching softwares on top of Jackrabbit Yes, sure. Maybe you want to cache on the application side. > CacheManager (Memory Management in Jackrabbit) > ---------------------------------------------- > > Key: JCR-619 > URL: https://issues.apache.org/jira/browse/JCR-619 > Project: Jackrabbit > Issue Type: New Feature > Components: jackrabbit-core > Reporter: Thomas Mueller > Assignee: 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. - You can reply to this email to add a comment to the issue online.