[
https://issues.apache.org/jira/browse/JCR-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682184#comment-13682184
]
Claus Köll commented on JCR-3605:
---------------------------------
Committed in revision 1492642 to trunk.
Committed in revision 1492643 to 2.6 branch
> 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öll
> Assignee: Claus Köll
> 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
> obtaining a lock from the internal XAReentrantLock. This leads to a deadlock
> situation if a other thread tries at the same time to use the
> LocalItemStateManager.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
