Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-8591

Conflict exception on commit

    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              mreutegg Marcel Reutegger
              Reporter:
              mreutegg Marcel Reutegger
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: