You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/06/16 19:24:24 UTC
[jira] Updated: (JCR-2598) Saving concurrent sessions executing
random operations causes a corrupt JCR
[ https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-2598:
-------------------------------
Status: Resolved (was: Patch Available)
Assignee: Jukka Zitting
Fix Version/s: 2.1.1
2.2.0
Resolution: Fixed
The remaining problems got fixed in JCR-2579.
I merged these changes also to the 2.1 branch for the 2.1.1 release.
> Saving concurrent sessions executing random operations causes a corrupt JCR
> ---------------------------------------------------------------------------
>
> Key: JCR-2598
> URL: https://issues.apache.org/jira/browse/JCR-2598
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.6.1, 2.0.0
> Reporter: Stephan Huttenhuis
> Assignee: Jukka Zitting
> Fix For: 2.1.1, 2.2.0
>
> Attachments: ConcurrencyTest3.java, JCR-2598-II.patch, JCR-2598.patch, org.apache.jackrabbit.core.ConcurrencyTest3.txt, Output after patch.txt, Output before patch.txt
>
>
> Run the attached unit test. Several concurrent sessions add, move, and remove nodes. Then the index is removed and the repository is again started. The repository is in an inconsistent state and the index cannot be rebuild. Also a lot of exceptions occur. See (see Output before patch.txt). Note that the unit test also suffers from the deadlock of issue http://issues.apache.org/jira/browse/JCR-2525 about half the time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.