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

Concurrent insert of new variables leads to FK Violations

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.1.0
    • None
    • engine
    • None

      Situation:
      Two concurrent transactions add a new variable to an execution.
      In this case, optimistic locking does not work since the row is freshly inserted. (cannot lock on non-existing row)
      As a result we end up with two rows which have the same execution id and the same name.
      When deleting the execution, only one of the rows is deleted which causes a Foreign Key constrain violation since the second row still references the Execution.

      Could be fixed with an integety constraint on EXECUTION_ID and NAME_ as well es TASK_ID_ and NAME_

      Failing testcase:
      https://github.com/camunda/camunda-bpm-platform/commit/6fffa99cbfe91204f402174349a8f1c87347efe1

      See also:
      https://groups.google.com/forum/?fromgroups#!topic/camunda-bpm-dev/WPHPzBCsTL0

        This is the controller panel for Smart Panels app

            [CAM-1574] Concurrent insert of new variables leads to FK Violations

            Daniel Meyer created issue -
            Daniel Meyer made changes -
            Description Original: Failing testcase:


            See also:
            https://groups.google.com/forum/?fromgroups#!topic/camunda-bpm-dev/WPHPzBCsTL0
            New: Situation:
            Two concurrent transactions add a new variable to an execution.
            In this case, optimistic locking does not work since the row is freshly inserted. (cannot lock on non-existing row)
            As a result we end up with two rows which have the same execution id and the same name.
            When deleting the execution, only one of the rows is deleted which causes a Foreign Key constrain violation since the second row still references the Execution.

            Could be fixed with an integety constraint on EXECUTION_ID and NAME_ as well es TASK_ID_ and NAME_

            Failing testcase:
            https://github.com/camunda/camunda-bpm-platform/commit/6fffa99cbfe91204f402174349a8f1c87347efe1

            See also:
            https://groups.google.com/forum/?fromgroups#!topic/camunda-bpm-dev/WPHPzBCsTL0
            Robert Gimbel made changes -
            Fix Version/s New: 7.0.6 [ 13090 ]
            Fix Version/s Original: 7.0.5 [ 13005 ]
            Daniel Meyer made changes -
            Link New: This issue is depended on by CAM-1688 [ CAM-1688 ]
            Daniel Meyer made changes -
            Assignee New: Daniel Meyer [ meyer ]
            Daniel Meyer made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Daniel Meyer made changes -
            Status Original: In Progress [ 3 ] New: Open [ 1 ]
            Daniel Meyer made changes -
            Assignee Original: Daniel Meyer [ meyer ]
            Robert Gimbel made changes -
            Rank New: Ranked higher
            Robert Gimbel made changes -
            Rank New: Ranked lower

              sebastian.menski Sebastian Menski
              meyer Daniel Meyer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: