From dev-return-13221-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Wed Aug 08 06:41:36 2007 Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 12258 invoked from network); 8 Aug 2007 06:41:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Aug 2007 06:41:35 -0000 Received: (qmail 42890 invoked by uid 500); 8 Aug 2007 06:41:29 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 42854 invoked by uid 500); 8 Aug 2007 06:41:29 -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 42818 invoked by uid 99); 8 Aug 2007 06:41:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2007 23:41:29 -0700 X-ASF-Spam-Status: No, hits=-99.8 required=10.0 tests=ALL_TRUSTED,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2007 06:41:16 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 693A171413F for ; Tue, 7 Aug 2007 23:40:59 -0700 (PDT) Message-ID: <28835123.1186555259428.JavaMail.jira@brutus> Date: Tue, 7 Aug 2007 23:40:59 -0700 (PDT) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Updated: (JCR-1050) Remove synchronization from JNDI data sources In-Reply-To: <15893455.1186017472985.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-1050: ------------------------------- Affects Version/s: (was: 1.3) (was: 1.2.2) (was: 1.2.1) (was: 1.2.3) (was: 1.1.1) (was: 1.1) (was: 1.0) (was: 0.9) (was: 1.0.1) (was: 1.3.1) (was: 1.4) (was: 2.0) This issue has been raised a few times before, and I agree with Padraic here. The synchronization issue hasn't been that pressing before since the SharedItemStateManager was using a workspace-global lock in any case, but with recent work that is no longer the case, and I see the database synchronization becoming a bottleneck. Pointers to some related discussions: http://www.nabble.com/Thoughts-on-database-persistence-tf1302987.html http://www.nabble.com/question-reagrding-JNDI-datasource-tf1760903.html http://www.nabble.com/DP-Persistence-manager-implementation-tf1045939.html http://www.nabble.com/Results-of-a-JR-Oracle-test-that-we-conducted-tf3333104.html http://www.nabble.com/DbFileSystem-and-SimpleDbPersistenceManager---Connection-and-PreparedStatement-tf1474979.html > Remove synchronization from JNDI data sources > --------------------------------------------- > > Key: JCR-1050 > URL: https://issues.apache.org/jira/browse/JCR-1050 > Project: Jackrabbit > Issue Type: Improvement > Components: core > Reporter: Padraic Hannon > Attachments: JNDI_Datasource_Changes.diff > > > Using datasources one should be able to rely on the application server to manage PreparedStatement caches therefore pre-creating and holding onto the connection for long periods of time should not be needed. This relates to improvement JCR-313, however, that change did not address the benefits one could see in using an application server controlled datasource. Even if jackrabbit does aim to use an embedded database such a system could be configured to use datasources and could benefit from the removal of the synchronization. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.