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

testAsyncModeWithParallelGateway fails when ActionNode is the last node executed in the parallel gateway

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.26.0.Final
    • 7.23.0.Final
    • KieServer
    • None
    • NEW
    • NEW
    • Hide

      execute mvn clean install -Dtest=AsyncContinuationSupportTest
      and check that the sequence is:
      Script Task-1
      Executing work item WorkItem 1 [name=Rest, state=0, processInstanceId=1, parameters

      {Method=GET, TaskName=Rest, Url=https://www.google.com}

      ]
      Script Task-2

      Show
      execute mvn clean install -Dtest=AsyncContinuationSupportTest and check that the sequence is: Script Task-1 Executing work item WorkItem 1 [name=Rest, state=0, processInstanceId=1, parameters {Method=GET, TaskName=Rest, Url=https://www.google.com} ] Script Task-2

      In the testAsyncModeWithParallelGateway, when the sequence in the gateway is:
      WorkItemHandler (REST call) -> ActionNode (Task Script-2)
      test fails, because it's not triggered the next node after Join.

      After finishing ActionNode (Task Script-2), the JoinNode (NodeInstanceImpl) returns false at checkAllActivated method, because it doesn't keep the previous result at the triggers map.

      So, even when triggers map was populated with (6,1) in the execution of the WorkItemHandler, this is not present in this instance of the JoinNode.

      This was not failing in previous versions of jbpm (i.e., 7.18.x)

        1. BPMN2-AsyncParallelGateway.jpg
          BPMN2-AsyncParallelGateway.jpg
          21 kB

              elguardian@gmail.com Enrique González Martínez (Inactive)
              gmunozfe@redhat.com Gonzalo Muñoz Fernández
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: