Job suspension state "null" for migrated start timer event

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.2.0, 7.1.1, 7.2.0-alpha1
    • Affects Version/s: None
    • Component/s: engine
    • None

      Steps to reproduce:

      • Deploy process with timer start event in camunda BPM 7.0.x
      • Migrate database to 7.1.0-Final
        => Timer start event job is not acquired because SUSPENSION_STATE_ is null

      Fix:

      • change job acquisition to acquire jobs with SUSPENSION_STATE_ null (this will fix problem for 7.2.x & 7.1.x)
      • add note to documentation to run additonal migration script (set SUSPENSION_STATE_ =1 where null). This covers community users using the 7.1.0.Final

        This is the controller panel for Smart Panels app

              Assignee:
              Michael Schoettes
              Reporter:
              Daniel Meyer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: