You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2010/01/13 22:45:54 UTC
[jira] Commented: (JCR-2456) Repository is corrupt after concurrent
changes with the same session
[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799949#action_12799949 ]
Marcel Reutegger commented on JCR-2456:
---------------------------------------
What's the performance impact of this patch? E.g. how much time does it take to save 1k added nodes with / without this patch?
> 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: 2.0-beta4
> Reporter: Thomas Mueller
> Attachments: 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.