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

DeploymentId not set on TimerEntity for TimerStartEvent

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.0.4, 7.1.0, 7.1.0-alpha1
    • 7.0.0, 7.0.3
    • engine
    • None

      See https://groups.google.com/forum/#!topic/camunda-bpm-users/Xes5msKoNhg

      Cause: deploymentId is not set on TimerEntity for timer start events. This causes the job to be acquired even though the process engine has configuration option isJobExecutorDeploymentAware=true

      The effect of this bug is that timer start event jobs are always acquired, regardless whether the deployment is currently activated or not.

        This is the controller panel for Smart Panels app

          1. start-timer.zip
            13 kB

              smirnov Roman Smirnov
              lipphardt Christian
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: