We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-3802

Cannot trigger non-interrupting message event subprocess in current process instance

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • 7.2.x, 7.3.x, 7.4.x
    • 7.2.0, 7.1.0, 7.3.0
    • engine
    • None

      Steps to reproduce:

      • process with non interrupting event suprocess with message start event
      • synchronous service task in the main flow which triggers the message event using api

      => Excecption

      Notes:
      1) The problem is that when the event suprocess is executed, the execution tree is expanded and the scope execution which executed the service task initially is replaced by a new concurrent execution which must be used for leaving the service task. This is not happening, hence the bug.

      2) Is it actually in tune with the specification for a process instance to "send itself a message?" - I think not but a) this has to be confirmed and b) we can decide to support it anyway. If we decide against it, a meaningful exception should be thrown when the user attempts to do this.

        This is the controller panel for Smart Panels app

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

            Cannot trigger non-interrupting message event subprocess in current process instance

              • Icon: Bug Report Bug Report
              • Resolution: Won't Fix
              • Icon: L3 - Default L3 - Default
              • 7.2.x, 7.3.x, 7.4.x
              • 7.2.0, 7.1.0, 7.3.0
              • engine
              • None

                Steps to reproduce:

                • process with non interrupting event suprocess with message start event
                • synchronous service task in the main flow which triggers the message event using api

                => Excecption

                Notes:
                1) The problem is that when the event suprocess is executed, the execution tree is expanded and the scope execution which executed the service task initially is replaced by a new concurrent execution which must be used for leaving the service task. This is not happening, hence the bug.

                2) Is it actually in tune with the specification for a process instance to "send itself a message?" - I think not but a) this has to be confirmed and b) we can decide to support it anyway. If we decide against it, a meaningful exception should be thrown when the user attempts to do this.

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        meyer Daniel Meyer
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              meyer Daniel Meyer
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              4 Start watching this issue

                                Created:
                                Updated:
                                Resolved: