The @Scheduled annotation in Spring v3.2.2 has added String parameters to the original 3 long parameters to handle this. fixedDelayString, fixedRateString and initialDelayString are now available too: @Scheduled(fixedDelayString = “${my.delay.property}”) public void someMethod(){ // perform something }
by default, spring uses a single-threaded Executor. so no two @Scheduled tasks will ever overlap. even two @Scheduled methods in completely unrelated classes will not overlap simply because there is only a single thread to execute all @Scheduled tasks. furthermore, even if you replace the default Executor with a thread pool based executor, those Executors … Read more
Using a Trigger you can calculate the next execution time on the fly. Something like this should do the trick (adapted from the Javadoc for @EnableScheduling): @Configuration @EnableScheduling public class MyAppConfig implements SchedulingConfigurer { @Autowired Environment env; @Bean public MyBean myBean() { return new MyBean(); } @Bean(destroyMethod = “shutdown”) public Executor taskExecutor() { return Executors.newScheduledThreadPool(100); … Read more
There is a ShedLock project that serves exactly this purpose. You just annotate tasks which should be locked when executed @Scheduled( … ) @SchedulerLock(name = “scheduledTaskName”) public void scheduledTask() { // do something } Configure Spring and a LockProvider @Configuration @EnableScheduling @EnableSchedulerLock(defaultLockAtMostFor = “10m”) class MySpringConfiguration { … @Bean public LockProvider lockProvider(DataSource dataSource) { return … Read more
Try with: @Scheduled(cron = “0 1 1 * * ?”) Below you can find the example patterns from the spring forum: * “0 0 * * * *” = the top of every hour of every day. * “*/10 * * * * *” = every ten seconds. * “0 0 8-10 * * *” … Read more