Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-3604

Foreign Key Constraint errors due to incorrect flush ordering

    XMLWordPrintable

    Details

      Description

      The method DbOperationManager#sortByReferences uses the cached entity state to compute the flush ordering. This need not necessarily reflect the state in the database.

      Example:
      Assume a persistent execution structure a <- b <- c
      In one transaction:
      1. remove b such that new tree is a <- c (can happen when concurrency ends and a concurrent parent is removed)
      2. Remove a and c

      The above-mentioned method now takes into account the relationship from a <- c, so the relation of c to b is ignored and the flushed DELETEs may be ordered incorrectly

      When fixing this, please re-add the failing test cases of CAM-3453

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: