jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Köll (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-2598) Saving concurrent sessions executing random operations causes a corrupt JCR
Date Fri, 01 Oct 2010 06:53:34 GMT

    [ https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916804#action_12916804
] 

Claus Köll commented on JCR-2598:
---------------------------------

Should we add the ConcurrencyTest3 to a TestSuite ?
As i can see the Testcase will not be executed at the Moment...

> 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: 1.6.4, 2.0.3, 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.


Mime
View raw message