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 3ECB51090B for ; Mon, 26 Aug 2013 05:52:56 +0000 (UTC) Received: (qmail 88127 invoked by uid 500); 26 Aug 2013 05:52:54 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 88050 invoked by uid 500); 26 Aug 2013 05:52:53 -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 88043 invoked by uid 99); 26 Aug 2013 05:52:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Aug 2013 05:52:51 +0000 Date: Mon, 26 Aug 2013 05:52:51 +0000 (UTC) From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (JCR-3655) Better Locking inside LockManagerImpl 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-3655?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Claus K=C3=B6ll updated JCR-3655: ---------------------------- Description:=20 Its possible to get a Deadlock during the TimeoutHandler is running. As tried to fix that problem in JCR-3605 i found that the problem is hard t= o fix because of locking the ItemStateManager during modifying the lock properties. It would be better t= o use a XAReentrantLock than the current synchronized block. was: Its possible to get a Deadlock during the TimeoutHandler is running. As tried to fix that problem in JCR-3605 i found that the problem is hard t= o fix because of locking the ItemStateManager during modifying the lock properties. It would be better t= o use a XAReentrantLock rather the current synchronized block. =20 > Better Locking inside LockManagerImpl > ------------------------------------- > > Key: JCR-3655 > URL: https://issues.apache.org/jira/browse/JCR-3655 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-core > Affects Versions: 2.6.2, 2.7 > Reporter: Claus K=C3=B6ll > Assignee: Claus K=C3=B6ll > > Its possible to get a Deadlock during the TimeoutHandler is running. > As tried to fix that problem in JCR-3605 i found that the problem is hard= to fix because of locking the > ItemStateManager during modifying the lock properties. It would be better= to use a XAReentrantLock than the current synchronized block. -- 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