[
https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-2456:
-------------------------------
Fix Version/s: core 1.4.12
1.6.2
I committed the backported patch to the 1.6 branch in revision 948488 and
backported/merged the changes further to the 1.4 branch in revision 948495.
> 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: core 1.4.12, 1.6.2, 2.0-beta6
>
> Attachments: patch-2456-1.5.txt, patch-2456-b-1.6.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.