You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Unico Hommes (JIRA)" <ji...@apache.org> on 2015/05/04 15:25:08 UTC
[jira] [Commented] (JCR-2598) Saving concurrent sessions executing
random operations causes a corrupt JCR
[ https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526621#comment-14526621 ]
Unico Hommes commented on JCR-2598:
-----------------------------------
Hi [~stanges],
Several bugs in this area have been identified and fixed since this issue was created. See for instance JCR-3501, JCR-3290, and JCR-3289. I spent a lot of effort to try to root out the various causes of repository inconsistencies and think most if not all of them have been fixed. We have very thorough tests that cover all possible combinations of operations with multiple sessions and cluster nodes alternating and we cannot reproduce any scenario anymore which results in repository inconsistencies. Our customers hardly ever encounter them anymore. In the event that an inconsistency does occur, the consistency checker has seen a lot of improvements. See JCR-3269, JCR-3267, JCR-3265, JCR-3263, and JCR-3525. I think this issue can be closed.
> 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)