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

Local variable instances are duplicated in the history when execution tree compaction happens

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.5.0, 7.5.0-alpha3
    • Component/s: engine
    • Labels:
      None

      Description

      Steps to reproduce:

      1. start a process instance of the as screenshot attached process
      2. set a local execution variable on user task B: runtimeService.setVariableLocal(B, "foo", "bar");
      3. complete user task A: taskService.complete(A);
      4. the engine performs internally an execution tree compaction

      Problem:
      In the history there are two historic variable instances of variable foo.

      Expected behavior:

      • the local variables are still present
      • the corresponding historic variable instance is updated and there does not exist a second historic variable instance for the variable foo

      Hint:
      The local variables are copied from the child execution to the parent execution.
      See failing test cases: https://github.com/camunda/camunda-bpm-platform/commit/9c85f156c058dcc4ab42f79c6dca546700178a26

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              meyer Daniel Meyer
              Reporter:
              roman.smirnov Roman Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: