You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Geoffroy Schneck (Commented) (JIRA)" <ji...@apache.org> on 2012/03/08 11:40:57 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=13225125#comment-13225125 ] 

Geoffroy Schneck commented on JCR-2598:
---------------------------------------

Comment from CQ user : 

Is there any setup where it's not recommended to set this property org.apache.jackrabbit.core.state.validatehierarchy to true ? 

If not, why not making setting it true by default ? 
                
> 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 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