Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1687

Reoccuring command not executed after temporary database unavailability

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.3.0.GA
    • 7.1.1.GA
    • jBPM Core
    • None

    • Ubuntu 18.04 (bionic)

    • CR1
    • Hide
      1. Schedule recurring command with long enough execution interval eg. 1 minute
      2. Shutdown database between two following executions
      3. Wait until next occurrence of command execution and startup database a few seconds after that one
      4. No further occurrence is executed
      Show
      Schedule recurring command with long enough execution interval eg. 1 minute Shutdown database between two following executions Wait until next occurrence of command execution and startup database a few seconds after that one No further occurrence is executed
    • 2018 Week 48-50

      Executor stops running reoccurring command after temporary database unavailability. It happens only when the database is unavailable in time of scheduled execution. If the database is unavailable between two following executions everything works fine.
      LoadAndScheduleRequestsTask logs point out that command is scheduled.

              swiderski.maciej Maciej Swiderski (Inactive)
              dariusz.uzar Dariusz Uzar (Inactive)
              Marian Macik Marian Macik
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: