Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Tue, 3 Sep 2013 07:15:51 +0000 (UTC)
From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12665453.1377496210654.70016.1378192551650@arcas>
In-Reply-To: <JIRA.12665453.1377496210654@arcas>
References: <JIRA.12665453.1377496210654@arcas>
Subject: [jira] [Commented] (JCR-3655) Better Locking inside LockManagerImpl
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-3655?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D137564=
07#comment-13756407 ]=20

Claus K=C3=B6ll commented on JCR-3655:
---------------------------------

Committed in revision 1519585 to trunk.
               =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
>         Attachments: JCR-3655.patch
>
>
> 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