Project Polygene has retired. For details please refer to its Attic page.
Scheduler
Zest™
Introduction
Tutorials
Javadoc
Samples
Core
Libraries
Extensions
Tools
Glossary 

Scheduler

code

docs

tests

The Scheduler library provides an easy way to schedule tasks using cron expressions if needed.

An optional Timeline allows you to browse past and future task runs.

Table 44. Artifact

Group IDArtifact IDVersion

org.qi4j.library

org.qi4j.library.scheduler

2.1


Logging

The SLF4J Logger used by this library is named "org.qi4j.library.scheduler".

Assembly

Use SchedulerAssembler to add the Scheduler service to your Application. This Assembler provide a fluent api to programmatically configure configuration defaults and activate the Timeline service assembly that allow to browse in past and future Task runs.

Here is a full example:

new SchedulerAssembler().visibleIn( Visibility.application )
    .withConfig( configModuleAssembly, Visibility.layer )
    .withTimeline()
    .assemble( moduleAssembly );

Configuration

SchedulerConfiguration defines configuration properties details:

/**
 * @return Number of worker threads, optional and defaults to the number of available cores.
 */
@Optional
Property<Integer> workersCount();

/**
 * @return Size of the queue to use for holding tasks before they are run, optional and defaults to 10.
 */
@Optional
Property<Integer> workQueueSize();

/**
 * @return If the scheduler must stop without waiting for running tasks, optional and defaults to false.
 */
@UseDefaults
Property<Boolean> stopViolently();

Writing Tasks

To write a schedulable Task, compose an Entity with the Task type to be able to schedule it.

The Task contract is quite simple:

public interface Task
    extends Runnable
{
    Property<String> name();

    @UseDefaults
    Property<List<String>> tags();
}

Tasks have a mandatory name property and an optional tags property. Theses properties get copied in each TimelineRecord created when the Timeline feature is activated.

The run() method of Tasks is wrapped in a UnitOfWork when called by the Scheduler. Thanks to the UnitOfWork handling in Zest, you can split the work done in your Tasks in several UnitOfWorks, the one around the Task#run() invocation will then be paused.

Here is a simple example:

interface MyTaskEntity extends Task
{
    Property<String> myTaskState();

    Association<AnotherEntity> anotherEntity();
}

class MyTaskMixin implements Runnable
{
    @This MyTaskEntity me;

    @Override
    public void run()
    {
        me.myTaskState().set(me.anotherEntity().get().doSomeStuff(me.myTaskState().get()));
    }
}

Scheduling Tasks

Tasks are scheduled using the Scheduler service. This creates a Schedule associated to the Task that allows you to know if it is running, to change it’s cron expression and set it’s durability.

By default, a Schedule is not durable. In other words, it do not survive an Application restart. To make a Schedule durable, set it’s durable property to true once its scheduled.

There are two ways to schedule a Task using the Scheduler service: once or with a cron expression.

Scheduling once

This is the easiest way to run a background Task once after a given initial delay in seconds.

@Service Scheduler scheduler;

public void method()
{
    MyTaskEntity myTask = todo();
    Schedule schedule = scheduler.scheduleOnce( myTask, 10, false );
    // myTask will be run in 10 seconds from now
}

Note that there is no point in making such a Schedule durable because it won’t be run repeatedly.

Scheduling using a cron expression

Cron expression parsing is based on the GNU crontab manpage that can be found here: http://unixhelp.ed.ac.uk/CGI/man-cgi?crontab+5 .

The following extensions are used:

  • a mandatory field is added at the begining: seconds.
  • a special string is added: @minutely
  • a special character is added: ? to choose between dayOfMonth and dayOfWeek

The ? special char has the same behavior as in the Quartz Scheduler expression. The wikipedia page http://en.wikipedia.org/wiki/CRON_expression explains Quartz Scheduler expression, not simple cron expressions. You’ll find there about the ? special char and maybe that some other extensions you would like to use are missing in this project.

To sum up, cron expressions used here have a precision of one second. The following special strings can be used:

  • @minutely
  • @hourly
  • @midnight or @daily
  • @weekly
  • @monthly
  • @annualy or @yearly

Durability

Schedules can either be ethereal or durable, passed as an argument to the Scheduler. If it is a durable schedule, then the Task must be an Entity Composite.

When the == Observing the Timeline ==

Timeline allow to browse in past and future Task runs. This feature is available only if you activate the Timeline assembly in the SchedulerAssembler}, see above.

Once activated, Task success and failures are recorded. Then, the Timeline service allow to browse in past (recorded) and in anticipated (future) Task runs.

Use the following in your code to get a Timeline Service injected:

@Service Timeline timeline;

Here is the actual Timeline contract:

public interface Timeline
{
  [...snip...]

    Iterable<TimelineRecord> getLastRecords( int maxResults );
      [...snip...]

    Iterable<TimelineRecord> getNextRecords( int maxResults );
      [...snip...]

    Iterable<TimelineRecord> getRecords( DateTime from, DateTime to );
      [...snip...]

    Iterable<TimelineRecord> getRecords( long from, long to );
}