Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1154

[GSS](7.0.z) Signal on boundary event causes an unwanted event listener message

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 7.0.0.GA
    • Business Central

    • RHPAM 7.0.0

    • Hide

      1. Import *.bpmn2 process attached to business-central (BPMS or RHBA);
      2. It will require a "brmsuser" set since there is an user task assigned to it (or just set another Actor for "SampleHT" existing User task placed inside subprocess);
      3. after build&deploy, start the process definition - it should get stopped in "SampleHT" user task;
      4. now send a signal "name: signalTest - value: signalTest" to this process instance;

      Result: At this point, the process instance is waiting an action in SampleHT user task. However, if you send a signal the catch signal event will fire anyway. So if you look now at nodeinstancelog table, it will have a register for that signal.

      5. Then, start and complete SampleHT User Task and send signal event to process instance again.

      Result: It is now waiting or signal get fired or InnerHT user task to be completed. Therefore, after sending a new signal... the catch signal event will be fired and process terminated.

      Show
      1. Import *.bpmn2 process attached to business-central (BPMS or RHBA); 2. It will require a "brmsuser" set since there is an user task assigned to it (or just set another Actor for "SampleHT" existing User task placed inside subprocess); 3. after build&deploy, start the process definition - it should get stopped in "SampleHT" user task; 4. now send a signal "name: signalTest - value: signalTest" to this process instance; Result: At this point, the process instance is waiting an action in SampleHT user task. However, if you send a signal the catch signal event will fire anyway. So if you look now at nodeinstancelog table, it will have a register for that signal. 5. Then, start and complete SampleHT User Task and send signal event to process instance again. Result: It is now waiting or signal get fired or InnerHT user task to be completed. Therefore, after sending a new signal... the catch signal event will be fired and process terminated.

      The process has an embedded subprocess and is in wait on the human task node.If you send a signal, even if the process is not waiting for that signal, the method (node) is executed;
      The catch signal event is fired even if the process instance is not waiting for that. In nodeinstancelog table is possible to see that there are two registers for that same signal node.

        1. org.jbpm.sample11.v1.0.bpmn2
          37 kB

              elguardian@gmail.com Enrique González Martínez (Inactive)
              rhn-support-ajuricic Amana Juricic
              Jan Hrcek Jan Hrcek (Inactive)
              Jan Hrcek Jan Hrcek (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: