[OAK-8591] Conflict exception on commit

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.8.0, 1.10.0, 1.12.0, 1.14.0, 1.16.0
• Fix Version/s: 1.18.0, 1.10.5, 1.8.17
• Component/s: documentmk
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 04/Sep/19 06:29
• Updated: 26/Sep/19 11:40
• Resolved: 10/Sep/19 13:16

Description

Under some conditions it may happen that a commit to the DocumentStore fails with a ConflictException even though there is no conflicting change. This includes regular commits as well as branch commits.

The actual problem is with NodeDocument.getNewestRevision(). This method is used in Commit.checkConflicts() to find out when the most recent change happened on a node and find conflicts. The returned value is incorrect and may e.g. return null even though the node exists. This will then trigger the ConflictException.