[
https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated JCR-2456:
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta6
Assignee: Thomas Mueller
Status: Resolved (was: Patch Available)
According to Tobi, the three nodes (VERSION_STORAGE_NODE_ID,
ACTIVITIES_NODE_ID, NODETYPES_NODE_ID) are the only (virtual) child nodes that
may exist. So this is fixed.
> Repository is corrupt after concurrent changes with the same session
> --------------------------------------------------------------------
>
> Key: JCR-2456
> URL: https://issues.apache.org/jira/browse/JCR-2456
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.7, 2.0-beta5
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 2.0-beta6
>
> Attachments: patch-2456-1.5.txt, patch-2456-b.txt, patch-2456.txt,
> TestMultiThread.java
>
>
> After concurrent write operations using the same session, the repository can
> get corrupt, meaning a ItemNotFoundException is thrown when trying to remove
> a node.
> Concurrent write operations are not supported, however I believe the
> persistent state of the repository should not be get corrupt.
> One way to solve this problem is to synchronize on the session internally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
