Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-8975

Terminating embedded event sub-process incorrectly terminates parent process

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • 7.24.0.Final
    • Runtime Engine
    • None
    • NEW
    • NEW
    • Hide

      1. Start a new case instance via REST API. Case instance is running with "Dummy User Task" and "Milestone 1" nodes started (ie "entered").
      2. Send "testSignal" signal from WB.
      3. Embedded event sup-process is triggered by the "testSignal" and executed successfully.
      4. Case instance is incorrectly terminated with both "Dummy User Task" and "Milestone 1" marked as completed.

      WB Log from the case instance:

      • a few seconds ago
        MilestoneNode 'Milestone 1' (System) node was COMPLETED
      • a few seconds ago
        Task 'Dummy User Task' (Human) node was COMPLETED
        Details
      • a few seconds ago
        EndNode (System) node was COMPLETED
      • a few seconds ago
        EndNode (System) node was ENTERED
      • a few seconds ago
        ActionNode 'Verify Update' (System) node was COMPLETED
      • a few seconds ago
        ActionNode 'Verify Update' (System) node was ENTERED
      • a few seconds ago
        ActionNode 'Signaled Script Task' (System) node was COMPLETED
      • a few seconds ago
        ActionNode 'Signaled Script Task' (System) node was ENTERED
      • a few seconds ago
        StartNode (System) node was COMPLETED
      • 3 minutes ago
        MilestoneNode 'Milestone 1' (System) node was ENTERED
      • 3 minutes ago
        Task 'Dummy User Task' (Human) node was ENTERED
        Details
      Show
      1. Start a new case instance via REST API. Case instance is running with "Dummy User Task" and "Milestone 1" nodes started (ie "entered"). 2. Send "testSignal" signal from WB. 3. Embedded event sup-process is triggered by the "testSignal" and executed successfully. 4. Case instance is incorrectly terminated with both "Dummy User Task" and "Milestone 1" marked as completed. WB Log from the case instance: a few seconds ago MilestoneNode 'Milestone 1' (System) node was COMPLETED a few seconds ago Task 'Dummy User Task' (Human) node was COMPLETED Details a few seconds ago EndNode (System) node was COMPLETED a few seconds ago EndNode (System) node was ENTERED a few seconds ago ActionNode 'Verify Update' (System) node was COMPLETED a few seconds ago ActionNode 'Verify Update' (System) node was ENTERED a few seconds ago ActionNode 'Signaled Script Task' (System) node was COMPLETED a few seconds ago ActionNode 'Signaled Script Task' (System) node was ENTERED a few seconds ago StartNode (System) node was COMPLETED 3 minutes ago MilestoneNode 'Milestone 1' (System) node was ENTERED 3 minutes ago Task 'Dummy User Task' (Human) node was ENTERED Details

    Description

      Hi,

      I have a Case project with an embedded event sub-process; when the sub-process is terminated, it also terminates the overall case (parent) process (see attached test case jar file).

      I have tried to terminate the embedded event sub-process with signal end event and the same result happens where the parent process/case terminates as soon as the embedded sub-process is exited/completed. When I added a user task to the embedded event sub-process before the signal end event to prevent the sub-process from completing, it kept the parent process/case alive.

      Attachments

        Activity

          People

            swiderski.maciej Maciej Swiderski (Inactive)
            datoslabs Eric Shieh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: