Engine startup can fail with OLE when re-configuring history cleanup job

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.9.0, 7.7.9, 7.8.5, 7.9.0-alpha4
    • Affects Version/s: 7.9.0-alpha3
    • Component/s: engine
    • None

      1. Configure a process engine with a job executor and history cleanup. This creates the cleanup job in the database. Have plenty of cleanable data around.
      2. Shutdown engine. Reconfigure cleanup job.
      3. Engine constructor: Job executor is started first. Assume it picks up the cleanup job immediately.
      4. Engine constructor: History job is reconfigured.
      5. If job execution finishes first, then updating the history job fails with OLE.
      6. Process engine constructor raises OptimisticLockingException
      7. Container startup fails (e.g. Tomcat)

        This is the controller panel for Smart Panels app

              Assignee:
              Yana Vasileva
              Reporter:
              Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: