From dev-return-9053-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Mon Oct 09 14:08:02 2006 Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 39763 invoked from network); 9 Oct 2006 14:08:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Oct 2006 14:08:02 -0000 Received: (qmail 25244 invoked by uid 500); 9 Oct 2006 14:08:01 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 25009 invoked by uid 500); 9 Oct 2006 14:08:00 -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 25000 invoked by uid 99); 9 Oct 2006 14:08:00 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Oct 2006 07:08:00 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jukka.zitting@gmail.com designates 66.249.82.231 as permitted sender) Received: from [66.249.82.231] (HELO wx-out-0506.google.com) (66.249.82.231) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Oct 2006 07:07:58 -0700 Received: by wx-out-0506.google.com with SMTP id t13so1630163wxc for ; Mon, 09 Oct 2006 07:07:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NVydKnl8aXoVfz8ivVXt5lnf4Kbg3TB4fSSkIS03BKK7jq+qd54PZqq8HROo7Kkaen6Dk6r7NEcVpwrDePeumyrhG/MRa9XnNAy9s0ysvXIsCdAGEWoeqdiQc0VbqOuE6OUKFt/oJWqV9DN4Qi+hedCoFA0qZjdUDjx2sDvoLuQ= Received: by 10.90.66.9 with SMTP id o9mr2558321aga; Mon, 09 Oct 2006 07:07:37 -0700 (PDT) Received: by 10.90.96.17 with HTTP; Mon, 9 Oct 2006 07:07:37 -0700 (PDT) Message-ID: <510143ac0610090707u27eaabc9lcda6c7615049406f@mail.gmail.com> Date: Mon, 9 Oct 2006 17:07:37 +0300 From: "Jukka Zitting" To: dev@jackrabbit.apache.org Subject: Re: About Issue JCR-546 In-Reply-To: <286825977104680910@unknownmsgid> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <286825977104680910@unknownmsgid> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, On 10/9/06, Ferdinand Chan wrote: > Can anyone explain a bit more on the JCR-546 issue? Does it implies that no > concurrent check-in can be performed within the system even different users > are checking in different nodes? I think so. There's also a long-lasting versioning vs. concurrency problem that's been a known issue for two years already, JCR-18. :-( My best advice for now has been to explicitly synchronize on the repository instance whenever you are doing versioning operations. Note that you can still do normal read and write operations concurrently with versioning, so this isn't as bad as it could be. Perhaps we should put that synchronization inside the versioning methods until the concurrency issues are solved... BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - info@yukatan.fi Software craftsmanship, JCR consulting, and Java development