Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B191BE717 for ; Fri, 14 Dec 2012 10:54:17 +0000 (UTC) Received: (qmail 6178 invoked by uid 500); 14 Dec 2012 10:54:14 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 6121 invoked by uid 500); 14 Dec 2012 10:54:14 -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 6071 invoked by uid 99); 14 Dec 2012 10:54:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Dec 2012 10:54:13 +0000 Date: Fri, 14 Dec 2012 10:54:13 +0000 (UTC) From: =?utf-8?Q?C=C3=A9dric_Damioli_=28JIRA=29?= To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (JCR-3485) The Datastore garbage collector does not work with a Derby-based DbDataStore MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JCR-3485?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] C=C3=A9dric Damioli updated JCR-3485: -------------------------------- Attachment: DbDataStore.patch =20 > The Datastore garbage collector does not work with a Derby-based DbDataSt= ore > -------------------------------------------------------------------------= --- > > Key: JCR-3485 > URL: https://issues.apache.org/jira/browse/JCR-3485 > Project: Jackrabbit Content Repository > Issue Type: Bug > Reporter: C=C3=A9dric Damioli > Attachments: DbDataStore.patch > > > We obtain a lot of Derby lock timeouts > Looking at the code, it seems that a few ResultSets are not actually clos= ed, leading to Derby keeping some locks=20 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira