I wanted to attach the file, but accidentally changed the status to "Patch Available" and fix version 1.5.7 with the submit patch option. I guess that probably should be reverted.
Bart On Thu, Jan 14, 2010 at 12:29 PM, Bart van der Schans (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Bart van der Schans updated JCR-2456: > ------------------------------------- > > Affects Version/s: (was: 2.0-beta4) > 1.5.7 > Status: Patch Available (was: Open) > >> 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 >> Reporter: Thomas Mueller >> Attachments: patch-2456-1.5.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. > > -- Hippo B.V. - Amsterdam Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466 Hippo USA Inc. - San Francisco 101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646 ----------------------------------------------------------------- http://www.onehippo.com - [email protected] -----------------------------------------------------------------
