jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-756) Concurrent add/remove child node operations in a cluster may corrupt repository.
Date Mon, 26 Feb 2007 16:43:05 GMT

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

Jukka Zitting commented on JCR-756:
-----------------------------------

Dominique, can you isolate the fix for just this issue from the 509624 commit? Otherwise I
can't include
this in the Jackrabbit 1.2.3 release, as the 509624 change is IMHO too large for a patch release.


> 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.2.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