[ https://issues.apache.org/jira/browse/OAK-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated OAK-8591: ---------------------------------- Priority: Critical (was: Blocker) > Conflict exception on commit > ---------------------------- > > Key: OAK-8591 > URL: https://issues.apache.org/jira/browse/OAK-8591 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk > Reporter: Marcel Reutegger > Assignee: Marcel Reutegger > Priority: Critical > Fix For: 1.18.0, 1.10.5, 1.8.17 > > > 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. -- This message was sent by Atlassian Jira (v8.3.2#803003)