jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-756) Concurrent add/remove child node operations in a cluster may corrupt repository.
Date Sat, 03 Mar 2007 18:11:50 GMT

    [ https://issues.apache.org/jira/browse/JCR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477661
] 

Dominique Pfister commented on JCR-756:
---------------------------------------

Jukka, sorry for not having answered to your question, was quite busy the last few days! I
quickly took a look at the changes I had to make in order to have the Create/Remove test scenario
pass in my already refactored classes, and those changes looked to complicated to be merged
back to the 1.2 branch.

> Concurrent add/remove child node operations in a cluster may corrupt repository.
> --------------------------------------------------------------------------------
>
>                 Key: JCR-756
>                 URL: https://issues.apache.org/jira/browse/JCR-756
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.1, 1.2.2
>            Reporter: Dominique Pfister
>         Assigned To: Dominique Pfister
>             Fix For: 1.3
>
>         Attachments: Create.java, Remove.java, repository.xml
>
>
> Concurrent add/remove child node operations in a cluster may store an inconsistent list
of child node entries, i.e. an entry in the list may appear that has no associated node. This
eventually results in an ItemNotFoundException, the next time one of these bogus entries is
accessed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message