Defect #2054
closed
Scheduler: scheduled task is skipped
100%
Description
Scheduled task can be skipped, if quartz thread pool is exhausted (all worker threads were busy running other jobs) or scheduler itself was down (e.g during application restart).
If this situation occurs, then scheduled LRT task (by cron trigger) is not executed.
Configure scheduler misfire handler policy properly to prevent skipping some jobs.
Workaroud: scheduler thead pool configuration can be changed in quartz.propereties (5 theads by default).
@all versions affected
Related issues
Updated by Radek Tomiška about 4 years ago
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Vít Švanda
- % Done changed from 0 to 90
Policy to process misfired trigger configured, commit:
https://github.com/bcvsolutions/CzechIdMng/commit/77db254af898614cdcbc50d389ef446107cdff34
Tasks will be processed after thread will be available, but execute time will don't respect the schedule (will be executed later) . But i hope is safer way than skip execution at all.
Could you provide me a feedback, please?
Updated by Vít Švanda about 4 years ago
- Status changed from Needs feedback to Resolved
- Assignee changed from Vít Švanda to Radek Tomiška
- % Done changed from 90 to 100
I did review and test. Scheduler still works :-).
Updated by Radek Tomiška about 4 years ago
- Status changed from Resolved to Closed
Updated by Radek Tomiška about 4 years ago
- Related to Defect #2207: LRT: Warning about task already running is logged repetitively added
Updated by Radek Tomiška about 4 years ago
- Related to deleted (Defect #2207: LRT: Warning about task already running is logged repetitively)
Updated by Radek Tomiška over 3 years ago
- Related to Task #2499: Scheduler - don't start the task when "Repeated start" fire time is in the past added
Updated by Radek Tomiška over 3 years ago
- Related to Task #2523: All scheduled tasks were started at once after IdM was down for longer time added