[
https://issues.apache.org/jira/browse/JCR-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-1461:
----------------------------------
Attachment: JCR-1461.patch
So far I haven't been able to reproduce the deadlock with a test.
Just looking at the thread dump we can avoid the deadlock by pulling the
getPath() in LockManagerImpl.getLockInfo() out of the acquire/release() scope.
I've attached a patch with that change.
Przemo, can you please build jackrabbit-core-1.3.4-rc1 again with this patch
applied and check if the deadlock still occurs?
It also seems that there's another thread involved in the deadlock. Can you
please attach the complete thread dump? Stripping off application specific
stack frames is of course OK.
> Deadlock on concurrent commit/checkin operations
> ------------------------------------------------
>
> Key: JCR-1461
> URL: https://issues.apache.org/jira/browse/JCR-1461
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.3.3, 1.3.4
> Reporter: Przemo Pakulski
> Priority: Critical
> Attachments: JCR-1461.patch, thread-dump.txt
>
>
> Running concurrently jackrabbit transactions including checkin operations
> leads to deadlock.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
