[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller updated JCR-2456: -------------------------------- Attachment: patch-2456-b.txt My original patch broke some version manager tests (for example org.apache.jackrabbit.test.api.version.ConfigurationsTest.testConfigurationsPath). I just made the test pass, and didn't try to understand what this test does exactly, and why the VersionManagerImpl does seem to store non-existing child nodes. Unless somebody objects, I will commit this patch later today. > 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 > 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.