[
https://issues.apache.org/jira/browse/JCR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676676#action_12676676
]
Jukka Zitting commented on JCR-1979:
------------------------------------
The deadlock seems to be a bit different, here we have two threads trying to
commit a transaction at the same time.
This should not be possible as all transactions will first acquire a write lock
on the shared version store before proceeding to XAItemStateManager.prepare.
I'll try to find out how the above could have happened.
> Deadlock on concurrent read & transactional write operations
> -------------------------------------------------------------
>
> Key: JCR-1979
> URL: https://issues.apache.org/jira/browse/JCR-1979
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Reporter: Przemo Pakulski
> Assignee: Jukka Zitting
> Fix For: 1.5.3
>
>
> Isuue has been introduced by resolving JCR-1755 (Transaction-safe
> versioning). This fixed changed sequence of commits, but at the same time
> order of acquiring locks has been disturbed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
