[
https://issues.apache.org/jira/browse/JCR-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802773#action_12802773
]
Thomas Mueller commented on JCR-2449:
-------------------------------------
Hi Martijn,
Thanks for your help. It's good to know the issue is resolved, and it's very
good to have the additional test case. For me, it is very important that the
check is disabled in Jackrabbit 2.0, because it is a major performance problem
in my environment.
> Slow performance due to JCR-2138 (Prevent persistence of faulty
> back-references)
> --------------------------------------------------------------------------------
>
> Key: JCR-2449
> URL: https://issues.apache.org/jira/browse/JCR-2449
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.7, 2.0-beta4
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 2.0.0
>
> Attachments: JCR-2449.patch
>
>
> In revision 782898, the following code was introduced:
> updateReferences() {
> for (Iterator i = local.addedStates(); i.hasNext();) {
> ...
> if (hasItemState(state.getId())) {
> ...
> }
> }
> }
> This will try to fetch inexistent nodes from the persistence manager.
> Depending on the persistence manager implementation, this is very slow.
> I hope there is a way to avoid this call, or if not, speed it up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
