[JCR-3738] CLONE - Deadlock on LOCAL_REVISION table in clustering environment

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Cannot Reproduce
• Affects Version/s: 2.6.2
• Component/s: clustering
• Environment: CQ5.6.1 with jackrabbit-core 2.6.2 backed off ibm db2 v10.5
• Assignee: Unassigned
• Reporter: Ankush Malhotra
• Created: 28/Feb/14 15:14
• Updated: 18/Dec/19 12:42
• Resolved: 22/Dec/17 04:58

Description

Original, cloned description:

> When inserting a lot of nodes concurrently (100/200 threads) the system hangs generating a deadlock on the LOCAL_REVISION table.
> There is a thread that starts a transaction but the transaction remains open, while another thread tries to acquire the lock on the table.
> This actually happen even if there is only a server up but configured in cluster mode.
> I found that in AbstractJournal, we try to write the LOCAL_REVISION even if we don't sync any record because they're generated by the same journal of the thread running.
>
> Removing this unnecessary (to me ) write to the LOCAL_REVISION table, remove the deadlock.

This might not be the exact same case with this issue. See the attached thread dumps etc. for full details.

Issue Links

• is a clone of: JCR-3440 Deadlock on LOCAL_REVISION table in clustering environment