Question 1

How do I schedule a job with cron expressions in Wisp?

Accepted Answer

You need to add the optional ch.eitchnet/cron dependency, then use CronExpressionSchedule.parse() or parseWithSeconds() to create schedules. For example, CronExpressionSchedule.parse('30 * * * *') runs a job every hour at minute 30.

Question 2

Wisp vs Quartz: which Java scheduler should I use?

Accepted Answer

Wisp is better for lightweight, simple scheduling with minimal dependencies, while Quartz suits complex, enterprise needs with features like clustering, persistence, and job stores. Choose Wisp for efficiency and Quartz for robustness.

Question 3

Does Wisp handle job persistence after an application restart?

Accepted Answer

No, Wisp does not provide built-in persistence; all job data is in-memory and lost on restart. You'd need to implement custom logic to save and reload job states.

Question 4

How can I monitor long-running jobs in Wisp?

Accepted Answer

Schedule a LongRunningJobMonitor with the scheduler, which logs warnings for jobs exceeding a configurable threshold. For example, new LongRunningJobMonitor(scheduler, Duration.ofMinutes(5)) checks every minute.

Question 5

What are the dependencies for using Wisp?

Accepted Answer

Wisp has zero dependencies except SLF4J for logging. However, cron expression support requires an additional lightweight library (ch.eitchnet/cron), which is optional but needed for cron features.

Question 6

Can I configure the thread pool to scale down idle threads in Wisp?

Accepted Answer

Yes, use SchedulerConfig.builder() to set threadsKeepAliveTime, allowing idle threads to be removed after a duration. For example, .threadsKeepAliveTime(Duration.ofHours(1)) scales down threads not used for an hour.

Wisp

What is Wisp?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions