[JCR-785] Updates to multiple workspaces (e.g. in a transaction) locked in cluster journal

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.1, 1.2.2, 1.2.3
• Fix Version/s: 1.3
• Component/s: jackrabbit-core
• Assignee: Dominique Pfister
• Reporter: Dominique Pfister
• Created: 12/Mar/07 09:15
• Updated: 25/Apr/07 08:45
• Resolved: 12/Mar/07 09:21

Description

Running a transaction that updates multiple workspaces (e.g. a versioning operation) will be locked, as they all try to acquire a non-reentrant lock in the cluster's journal. Short-term fix is to make the lock re-entrant. In the long run, a transaction context sensitive lock may be more appropriate.

How to reproduce: enable clustering in the test environment and let the test o.a.j.core.XATest.testSetVersionLabel() run. This will result in a deadlock when committing the operation.

This was initially reported by Rafał Kwiecień as a problem when using springmodules and clustering but turned out to be general problem with transactions and clustering. Thanks for reporting it!