jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3016) inconsistent repository after overlapping node add operations
Date Fri, 08 Jul 2011 13:04:17 GMT

     [ https://issues.apache.org/jira/browse/JCR-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Julian Reschke updated JCR-3016:

    Attachment: OverlappingNodeAddTest.java

Enhanced the diagnostics from the test case; it now clearly shows that session 1's "folder"
node is disconnected from it's parent, but stays in the repository (as demonstrated using

> inconsistent repository after overlapping node add operations
> -------------------------------------------------------------
>                 Key: JCR-3016
>                 URL: https://issues.apache.org/jira/browse/JCR-3016
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Julian Reschke
>         Attachments: OverlappingNodeAddTest.diff, OverlappingNodeAddTest.java
> It seems I can reproduce a sequence of operations that cause the repository to be inconsistent.
> The short version: 2 sessions add a same-named child node to the same parent folder (not
allowing same-name-siblings). Session 1's save() succeeds. Session 2's save() fails, but succeeds
on retry (!).
> After the operation, the child node created by session 1 is still present, but the parent
doesn't list it as child node anymore.
> (will add test case)

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message