Actions
Task #2523
open
All scheduled tasks were started at once after IdM was down for longer time
Status:
New
Priority:
High
Assignee:
Radek Tomiška
Category:
Scheduler
Target version:
-
Start date:
10/16/2020
Due date:
% Done:
0%
Estimated time:
Owner:
Description
Version 10.4.7
This happened in my local environment, but I think it's potentially dangerous for production usage (e.g. when there is some longer shutdown, either planned or not planned).
This happened in my local environment, but I think it's potentially dangerous for production usage (e.g. when there is some longer shutdown, either planned or not planned).
- IdM (Tomcat) didn't run for some time (more than 1 day)
- I started the Tomcat
- All tasks, that are scheduled, started almost immediately at once.
Expected behavior: The tasks run at their schedule time first time in the future.
Reason: The scheduled times ensure some order and distribution of the tasks. There can be good reasons why something should run only at specific time (e.g. notifications, dependency on the timing of some external operation). Also some of the "maintenance" tasks should run only at night, they could consume a lot of time or resources.
Maybe this is connected to #2499, but that ticket can happen only by some mistake, so I think this is more critical.
Related issues
Updated by Radek Tomiška over 3 years ago
- Related to Defect #2054: Scheduler: scheduled task is skipped added
Actions