Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 80436 invoked from network); 21 Apr 2006 13:11:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Apr 2006 13:11:32 -0000 Received: (qmail 38681 invoked by uid 500); 21 Apr 2006 13:11:32 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 38666 invoked by uid 500); 21 Apr 2006 13:11:31 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 38657 invoked by uid 99); 21 Apr 2006 13:11:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Apr 2006 06:11:31 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [217.146.177.59] (HELO web26512.mail.ukl.yahoo.com) (217.146.177.59) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 21 Apr 2006 06:11:30 -0700 Received: (qmail 69827 invoked by uid 60001); 21 Apr 2006 13:11:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=r6uf02jCTpF4c14b1DmoCC7reNAA5En+BlPzlKYCRXXH1UnatAIff3ITKmpw3Cm3Pt4OIizYnb0uWAROH8nVdEl932JVsyuR+Bn8aBGNkB+56w+fmmyPjxU1T7zObcNjfq/u66XPcPvtNsLs5j1ECSTYQxQQQlN1Zuv69GzHo00= ; Message-ID: <20060421131109.69825.qmail@web26512.mail.ukl.yahoo.com> Received: from [202.7.176.132] by web26512.mail.ukl.yahoo.com via HTTP; Fri, 21 Apr 2006 14:11:09 BST Date: Fri, 21 Apr 2006 14:11:09 +0100 (BST) From: Felix Satyaputra Subject: Re: DbFileSystem and SimpleDbPersistenceManager - Connection and PreparedStatement To: users@jackrabbit.apache.org In-Reply-To: <90a8d1c00604210530o573d04c9hbf1f1e9e6713e188@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Stefan, > the .lock file has nothing to do with it. it just > prevents > multiple RepositoryImpl instantiation using the same > configuration. I see. > write operations on the persistence layer are > synchronized > on a higher level in order to guarantee data > consistency/ > referential integrity (e.g. node references). > > see SharedItemStateManager#begin, #end and #cancel > methods. I've checked SharedItemStateManager#begin, #end and #cancel. So basically SharedItemStateManager manages the concurrency of the read/write operations by using the ReadWriteLock - within the same thread? I notice that the ReadWriteLock is being used in #begin, #end, and #cancel. Am I understanding this correctly? So it's not the PersistenceManager's responsibility to manage the concurrency of the read/write operation? Cheers, Felix Send instant messages to your online friends http://uk.messenger.yahoo.com