Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 58791 invoked from network); 15 Feb 2006 21:55:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Feb 2006 21:55:50 -0000 Received: (qmail 65799 invoked by uid 500); 15 Feb 2006 21:55:49 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 65788 invoked by uid 99); 15 Feb 2006 21:55:49 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2006 13:55:47 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 9B8E9183 for ; Wed, 15 Feb 2006 22:55:11 +0100 (CET) Message-ID: <679697298.1140040511635.JavaMail.jira@ajax.apache.org> Date: Wed, 15 Feb 2006 22:55:11 +0100 (CET) From: "Jukka Zitting (JIRA)" To: jackrabbit-dev@incubator.apache.org Subject: [jira] Updated: (JCR-314) Fine grained locking in SharedItemStateManager In-Reply-To: <726865404.1138964403203.JavaMail.jira@ajax.apache.org> 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 [ http://issues.apache.org/jira/browse/JCR-314?page=all ] Jukka Zitting updated JCR-314: ------------------------------ Fix Version: 1.1 Version: 0.9 > Fine grained locking in SharedItemStateManager > ---------------------------------------------- > > Key: JCR-314 > URL: http://issues.apache.org/jira/browse/JCR-314 > Project: Jackrabbit > Type: Improvement > Components: core > Versions: 0.9 > Reporter: Marcel Reutegger > Priority: Minor > Fix For: 1.1 > > The SharedItemStateManager (SISM) currently uses a simple read-write lock to ensure data consistency. Store operations to the PersistenceManager (PM) are effectively serialized. > We should think about more sophisticated locking to allow concurrent writes on the PM. > One possible approach: > If a transaction is currently storing data in a PM a second transaction may check if the set of changes does not intersect with the first transaction. If that is the case it can safely store its data in the PM. > This fine grained locking must also be respected when reading from the SISM. A read request for an item that is currently being stored must be blocked until the store is finished. -- 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