org.quartz.examples
Class ClusterTest

java.lang.Object
  |
  +--org.quartz.examples.ClusterTest

public class ClusterTest

extends java.lang.Object

Used to test/show the clustering features of JDBCJobStore (JobStoreTX or JobStoreCMT).

All instances MUST use a different properties file, because their instance Ids must be different, however all other properties should be the same.

If you want it to clear out existing jobs & triggers, pass a command-line argument called "clearJobs".

You should probably start with a "fresh" set of tables (assuming you may have some data lingering in it from other tests), since mixing data from a non-clustered setup with a clustered one can be bad.

Try killing one of the cluster instances while they are running, and see that the remaining instance(s) recover the in-progress jobs. Note that detection of the failure may take up to 15 or so seconds with the default settings.

Also try running it with/without the shutdown-hook plugin registered with the scheduler. (org.quartz.plugins.management.ShutdownHookPlugin).

Note: Never run clustering on separate machines, unless their clocks are synchronized using some form of time-sync service (daemon).

Author:

James House

See Also:

DumbRecoveryJob

Constructor Summary

ClusterTest()

Method Summary

static void	clusterTest(SchedulerFactory sf, boolean clearJobs, boolean scheduleJobs)
static void	main(java.lang.String[] args)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ClusterTest

public ClusterTest()

Method Detail

clusterTest

public static void clusterTest(SchedulerFactory sf,
                               boolean clearJobs,
                               boolean scheduleJobs)
                        throws java.lang.Exception

main

public static void main(java.lang.String[] args)
                 throws java.lang.Exception