[
https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526674#comment-14526674
]
Sam Stange commented on JCR-2598:
---------------------------------
We tried to run the consistency checker in fix mode, but our attempt failed.
For us, running the consistency checker took 2 days to complete, and only
resulted in an error when it attempted to fix the inconsistent nodes. We've
been trying to reproduce the scenario that would have caused this scenario, but
haven't been able to do so. We've identified a lot of, "it could be this or
that", but nothing has been able to reproduce the corruption.
> Saving concurrent sessions executing random operations causes a corrupt JCR
> ---------------------------------------------------------------------------
>
> Key: JCR-2598
> URL: https://issues.apache.org/jira/browse/JCR-2598
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.6.1, 2.0
> Reporter: Stephan Huttenhuis
> Assignee: Jukka Zitting
> Fix For: 1.6.4, 2.0.3, 2.1.1, 2.2
>
> Attachments: ConcurrencyTest3.java, JCR-2598-II.patch,
> JCR-2598.patch, Output after patch.txt, Output before patch.txt,
> org.apache.jackrabbit.core.ConcurrencyTest3.txt
>
>
> Run the attached unit test. Several concurrent sessions add, move, and remove
> nodes. Then the index is removed and the repository is again started. The
> repository is in an inconsistent state and the index cannot be rebuild. Also
> a lot of exceptions occur. See (see Output before patch.txt). Note that the
> unit test also suffers from the deadlock of issue
> http://issues.apache.org/jira/browse/JCR-2525 about half the time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
