jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2407) Make the disk space used by cached binary properties configurable
Date Wed, 25 Nov 2009 10:05:39 GMT

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

Thomas Mueller commented on JCR-2407:

This sounds more like a bug than like an improvement. 

In any case, a reproducible test case would help a lot. Also, we would need to know the configuration
(repository.xml and workspace.xml) and 
Jackrabbit version where it occurs.

> Make the disk space used by cached binary properties configurable
> -----------------------------------------------------------------
>                 Key: JCR-2407
>                 URL: https://issues.apache.org/jira/browse/JCR-2407
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.0-beta1
>            Reporter: Martijn Hendriks
> Binary properties which are in Jackrabbit's caches (SharedItemStateManager eg) are stored
on disk in the temp dir. This can cause problems on small temporary file systems as the size
of the binary properties on disk is not limited by Jackrabbit. There is one way to influence
this indirectly: make the Jackrabbit cache sizes smaller (via the CacheManager). It could
be helpful in some cases if an upper bound on the disk usage can be given. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message