[
https://issues.apache.org/jira/browse/JCR-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-1480.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5
XAVersionManager now only participates in XATransaction when there are version
operations.
Fixed in trunk in revision: 637865
> Deadlock when executing Version operations
> ------------------------------------------
>
> Key: JCR-1480
> URL: https://issues.apache.org/jira/browse/JCR-1480
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core, versioning
> Affects Versions: 1.4, core 1.4.1
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 1.5
>
>
> This only happens when a XA transaction is committed without changes. In
> XAVersionManager there is a check in the InternalXAResource returned by
> getXAResourceBegin(), which only acquires the write lock on the version
> manager if there are version related changes in the transaction. This kind of
> check is missing in the methods XAVersionManager.prepare/commit/rollback().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
