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

NullPointerException when escalating to a event subprocess more often than once

    XMLWordPrintable

    Details

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

      Description

      When starting this process and completing User Task 1, the engine runs into a NullpointerException (stacktrace attached to this issue):

      Please find the failing test case here: https://github.com/camunda/camunda-bpm-assert-scenario/blob/master/test/test-7.5/src/test/java/org/camunda/bpm/scenario/test/escalations/EscalationEventSubProcessTriggeredTwiceConventionalTest.java#L19

      Additional observations:

      1. When completing the User Task 2 first, the test runs through and reaches the End Event of the Sub Process twice, as expected. My impression - also because I already saw that in other tests - is that the fact that a sub process execution is still running is necessary to see this effect.
      2. The same scenario using boundary events works as expected: the End Event after the boundary escalation event is reached twice, regardless of completing User Task 1 first or the first instance of User Task 2 first... you find the fully working test case in the same folder as the failing test case linked above
      3. The NullPointerException also happens when only using intermediate events - showing that it is not related to reaching the end event of the process instance. I attached another diagram to show that other failing scenario. The failing test case for this second diagram is here: https://github.com/camunda/camunda-bpm-assert-scenario/blob/master/test/test-7.5/src/test/java/org/camunda/bpm/scenario/test/escalations/EscalationEventSubProcessTriggeredTwiceIntermediateConventionalTest.java#L19

        Attachments

          Activity

            People

            Assignee:
            johannes.heinemann Johannes Heinemann
            Reporter:
            martin@schimak.at Martin Schimak
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: