Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Thu, 13 Jun 2013 07:28:23 +0000 (UTC)
From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12652016.1370864628942.108188.1371108503225@arcas>
In-Reply-To: <JIRA.12652016.1370864628942@arcas>
References: <JIRA.12652016.1370864628942@arcas>
Subject: [jira] [Updated] (JCR-3605) Possible Deadlock during TimeoutHandler
 is running
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JCR-3605?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus K=C3=B6ll updated JCR-3605:
----------------------------

    Affects Version/s:     (was: 2.6.1)
                       2.6.2
   =20
> Possible Deadlock during TimeoutHandler is running
> --------------------------------------------------
>
>                 Key: JCR-3605
>                 URL: https://issues.apache.org/jira/browse/JCR-3605
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.6.2
>            Reporter: Claus K=C3=B6ll
>            Assignee: Claus K=C3=B6ll
>             Fix For: 2.6.3, 2.7.1
>
>         Attachments: JCR-3605.patch
>
>
> It's possible to create a deadlock while TimeoutHandler is running.
> The TimeoutHandler owns a monitor lock on LocalItemStateManager without o=
btaining a lock from the internal XAReentrantLock. This leads to a deadlock=
 situation if a other thread tries at the same time to use the LocalItemSta=
teManager.

--
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