Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Mon, 17 Dec 2012 09:48:12 +0000 (UTC)
From: "Alexander Muthmann (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12554903.1336741898365.15884.1355737692955@arcas>
In-Reply-To: <JIRA.12554903.1336741898365@arcas>
References: <JIRA.12554903.1336741898365@arcas>
Subject: [jira] [Commented] (JCR-3305) spi2davex.RepositoryServiceImpl ->
 idUriCache raises until heap overflow
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alexander Muthmann commented on JCR-3305:
-----------------------------------------

This issue can be resolved by using an LRU Cache with a fixed max-size instead of the two HashMaps currently used in IdURICache.java. 
                
> spi2davex.RepositoryServiceImpl -> idUriCache raises until heap overflow
> ------------------------------------------------------------------------
>
>                 Key: JCR-3305
>                 URL: https://issues.apache.org/jira/browse/JCR-3305
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-spi2dav
>            Reporter: Daniel Draeger
>
> from class URIResolverImpl:
> // TODO: to-be-fixed. uri/id-caches don't get updated
> While querying the JCR, it seems that the queryPath of each result property of each node is cached within the idUriCache and the cache is never cleaned up.
> - cleaning the cache
> - configurable parameter for max cache size should be available

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira