Wisp alternatives and similar libraries
Based on the "Job Scheduling" category.
Alternatively, view Wisp alternatives based on common mentions on social networks and blogs.
5.0 7.3 Wisp VS easy-batchSet up batch jobs with simple processing pipelines. Records are read in sequence from a data source, processed in pipeline and written in batches to a data sink.
3.9 9.1 Wisp VS JobRunrJob scheduling library which utilizes lambdas for fire-and-forget, delayed and recurring jobs. Guarantees execution by single scheduler instance using optimistic locking. Has features for persistence, minimal dependencies and is embeddable.
Do you think we are missing an alternative of Wisp or a related project?
Wisp is a library for managing the execution of recurring Java jobs.
It works like the Java class
ScheduledThreadPoolExecutor, but it comes with some advanced features:
- Jobs can be scheduled to run according to: a fixed hour (e.g. 00:30), a CRON expression, or a custom code-based expression,
- Statistics about each job execution can be retrieved,
- A too long jobs detection mechanism can be configured,
- The thread pool can be configured to scale down when there is less jobs to execute concurrently.
Wisp weighs only 30Kb and has zero dependency except SLF4J for logging. It will try to only create threads that will be used: if one thread is enough to run all the jobs, then only one thread will be created. A second thread will generally be created only when 2 jobs have to run at the same time.
The scheduler precision will depend on the system load. Though a job will never be executed early, it will generally run after 1ms of the scheduled time.
Wisp is compatible with Java 8 and higher.
Include Wisp in your project:
<dependency> <groupId>com.coreoz</groupId> <artifactId>wisp</artifactId> <version>2.2.0</version> </dependency>
Schedule a job:
Scheduler scheduler = new Scheduler(); scheduler.schedule( () -> System.out.println("My first job"), // the runnable to be scheduled Schedules.fixedDelaySchedule(Duration.ofMinutes(5)) // the schedule associated to the runnable );
A project should generally contain only one instance of a
So either a dependency injection framework handles this instance,
or either a static instance of
Scheduler should be created.
In production, it is generally a good practice to configure the monitor for long running jobs detection.
Changelog and upgrade instructions
All the changelog and the upgrades instructions are available in the project releases page.
When a job is created or done executing, the schedule associated to the job is called to determine when the job should next be executed. There are multiple implications:
- the same job will never be executed twice at a time,
- if a job has to be executed at a fixed frequency,
then the job has to finish running before the next execution is scheduled ;
else the next execution will likely be skipped (depending of the
Basics schedules are referenced in the
fixedDelaySchedule(Duration): execute a job at a fixed delay after each execution
executeAt(String): execute a job at the same time every day, e.g.
Schedules are very flexible and can easily be composed, e.g:
Schedules.afterInitialDelay(Schedules.fixedDelaySchedule(Duration.ofMinutes(5)), Duration.ZERO): the job will be first executed ASAP and then with a fixed delay of 5 minutes between each execution,
Schedules.executeOnce(Schedules.executeAt("05:30")): the job will be executed once at 05:30.
Schedules.executeOnce(Schedules.fixedDelaySchedule(Duration.ofSeconds(10))): the job will be executed once 10 seconds after it has been scheduled.
<dependency> <groupId>com.cronutils</groupId> <artifactId>cron-utils</artifactId> <version>9.1.5</version> </dependency>
Then to create a job which is executed every hour at the 30th minute,
you can create the schedule:
CronSchedule.parseQuartzCron("0 30 * * * ? *").
Cron expression should be created and checked using a tool like Cron Maker.
Custom schedules can be created, see the [Schedule](src/main/java/com/coreoz/wisp/schedule/Schedule.java) interface.
Schedules can reference a past time. However once a past time is returned by a schedule, the associated job will never be executed again. At the first execution, if a past time is referenced a warning will be logged but no exception will be raised.
Two methods enable to fetch scheduler statistics:
Scheduler.jobStatus(): To fetch all the jobs executing on the scheduler. For each job, these data are available:
- status (see
- executions count,
- last execution start date,
- last execution end date,
- next execution date.
Scheduler.stats(): To fetch statistics about the underlying thread pool:
- min threads,
- max threads,
- active threads running jobs,
- idle threads,
- largest thread pool size.
Long running jobs detection
To detect jobs that are running for too long, an optional job monitor is provided. It can be setup with:
scheduler.schedule( "Long running job monitor", new LongRunningJobMonitor(scheduler), Schedules.fixedDelaySchedule(Duration.ofMinutes(1)) );
This way, every minute, the monitor will check for jobs that are running for more than 5 minutes. A warning message with the job stack trace will be logged for any job running for more than 5 minutes.
The detection threshold can also be configured this way:
new LongRunningJobMonitor(scheduler, Duration.ofMinutes(15))
Scalable thread pool
By default the thread pool size will only grow up, from 0 to 10 threads (and not scale down). But it is also possible to define a maximum keep alive duration after which idle threads will be removed from the pool. This can be configured this way:
Scheduler scheduler = new Scheduler( SchedulerConfig .builder() .minThreads(2) .maxThreads(15) .threadsKeepAliveTime(Duration.ofHours(1)) .build() );
In this example:
- There will be always at least 2 threads to run the jobs,
- The thread pool can grow up to 15 threads to run the jobs,
- Idle threads for at least an hour will be removed from the pool, until the 2 minimum threads remain.