[ https://issues.apache.org/jira/browse/OAK-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922452#comment-16922452 ]
Marcel Reutegger edited comment on OAK-8591 at 9/10/19 10:07 AM: ----------------------------------------------------------------- Added ignored tests to trunk that reproduce the problem: http://svn.apache.org/r1866382 and http://svn.apache.org/r1866697 was (Author: mreutegg): Added ignored tests to trunk that reproduce the problem: http://svn.apache.org/r1866382 > 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: Blocker > 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)