You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2011/07/09 18:33:01 UTC
[jira] [Resolved] (JCR-3016) inconsistent repository after
overlapping node add operations
[ https://issues.apache.org/jira/browse/JCR-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg resolved JCR-3016.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
fixed in svn revision 1144695
> 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
> Assignee: Stefan Guggisberg
> Fix For: 2.3.0
>
> 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