[
https://issues.apache.org/jira/browse/JCR-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225263#comment-13225263
]
angela commented on JCR-3254:
-----------------------------
while i agree that it was useful for problem analysis, i somehow dislike the
idea of having the size configurable with the acprovider config.
the main reason is that i wouldn't want to be stuck with that implementation
which imo has some fundamental drawbacks (e.g. perm eval
only calculated on access).
using a system property for analysis was fine for me if it was not part of an
official release but only some sort of analysis-patch that
is used temporarily.
> make max size of CachingEntryCollector's cache configurable
> -----------------------------------------------------------
>
> Key: JCR-3254
> URL: https://issues.apache.org/jira/browse/JCR-3254
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.2.11, 2.4
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.12, 2.4.1, 2.6
>
>
> To assist in analyzing the bottleneck it would be good if it was easy to
> change the max size, currently hard-wired to 5000. Suggest to be pragmatic
> and do that through a system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
