Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-5173

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

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 6.4.9
    • Fix Version/s: None
    • Component/s: Business Central
    • Labels:
    • Environment:

      BPM Suite 6.4.9

    • Target Release:
    • Steps to Reproduce:
      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.

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  elguardian Enrique González Martínez
                  Reporter:
                  asamara Amana Juricic
                  Tester:
                  Marian Macik
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: