Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 90093 invoked from network); 31 May 2006 20:13:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 May 2006 20:13:25 -0000 Received: (qmail 98801 invoked by uid 500); 31 May 2006 20:13:23 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 98424 invoked by uid 500); 31 May 2006 20:13:21 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 98415 invoked by uid 99); 31 May 2006 20:13:21 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 May 2006 13:13:21 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 May 2006 13:13:21 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C2FF07141ED for ; Wed, 31 May 2006 20:12:29 +0000 (GMT) Message-ID: <8681703.1149106349781.JavaMail.jira@brutus> Date: Wed, 31 May 2006 20:12:29 +0000 (GMT+00:00) From: "Tobias Bocanegra (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Created: (JCR-449) inconsistency in internal version items during commits MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N inconsistency in internal version items during commits ------------------------------------------------------ Key: JCR-449 URL: http://issues.apache.org/jira/browse/JCR-449 Project: Jackrabbit Type: Bug Versions: 1.0, 1.0.1 Environment: r410655. Reporter: Tobias Bocanegra since some of the versioing information is somehow cached in the 'IternalVersionItems', it can happen that they are not updated fast enough after a commit that included versioning operations. subsequent versioing operations could leed to errors. test case: create 2 threads, that concurrently do: begin -> checkout -> checkin -> commit on the same node. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira