Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <10825698.7991271670294938.JavaMail.jira@thor>
Date: Mon, 19 Apr 2010 05:44:54 -0400 (EDT)
From: "Stephan Huttenhuis (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2598) Saving concurrent sessions executing
 random operations causes a corrupt JCR
In-Reply-To: <1760863561.6711270820390781.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Huttenhuis updated JCR-2598:
------------------------------------

    Attachment: JCR-2598-II.patch

> 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
>         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.