Re: Scheduler behaviour in case it is not running at the time where a job was supposed to be executed

I created https://issues.apache.org/jira/browse/SLING-5974 for making it possible to configure the misfire behaviour through the Sling Scheduler API. > On 18 Aug 2016, at 11:12, Konrad Windszus wrote: > > The default behaviour of Quartz seems to be a different one: >

Re: Scheduler behaviour in case it is not running at the time where a job was supposed to be executed

Hmm, I tend to disagree here. I dug deep into the code and com.adobe.granite.maintenance.impl.TaskSchedulerImpl is internally relying on org.apache.sling.commons.scheduler.Scheduler. Konrad > On 18 Aug 2016, at 11:11, Carsten Ziegeler wrote: > >> This is not what I

Re: Scheduler behaviour in case it is not running at the time where a job was supposed to be executed

The default behaviour of Quartz seems to be a different one: https://dzone.com/articles/quartz-scheduler-misfire MISFIRE_INSTRUCTION_FIRE_ONCE_NOW, which means a misfired execution (e.g. a missed cron time) leads to the immediate execution

Re: Scheduler behaviour in case it is not running at the time where a job was supposed to be executed

> This is not what I experience (I only tried with AEM 6.1 SP2 where > maintenance tasks are executed with a scheduler). The jobs are executed > immediately after the computer is waking up even if that is hours after the > scheduled time. > Maintenance tasks is an AEM feature which is not

Re: Scheduler behaviour in case it is not running at the time where a job was supposed to be executed

This is not what I experience (I only tried with AEM 6.1 SP2 where maintenance tasks are executed with a scheduler). The jobs are executed immediately after the computer is waking up even if that is hours after the scheduled time. > On 18 Aug 2016, at 10:55, Carsten Ziegeler

Re: Scheduler behaviour in case it is not running at the time where a job was supposed to be executed

> How does the Sling Scheduler behave in case two jobs are scheduled with a > cron expression (one at 1am, one at 2am on a daily basis) and Sling is either > not running or the computer is in sleep mode at that time? > Will both be executed immediately when the Sling Scheduler is active again?

Scheduler behaviour in case it is not running at the time where a job was supposed to be executed

How does the Sling Scheduler behave in case two jobs are scheduled with a cron expression (one at 1am, one at 2am on a daily basis) and Sling is either not running or the computer is in sleep mode at that time? Will both be executed immediately when the Sling Scheduler is active again? What