camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From C├ędric Pineau <>
Subject Quartz stateful job routes not recreated on server restart
Date Tue, 06 Sep 2011 14:39:59 GMT
Hi to all.

I use quartz stateful job with a jdbcstore.
Everything works fine as long as the server is not shutdown : the job is
running, its state is persisted.

But on server restart, the jobs are not running anymore, no exception in
trace, no nothing :-/
Still I get this trace on startup, indicating that a persisted job has been
found :
[INFO] core.QuartzScheduler Scheduler meta-data: Quartz Scheduler (v1.8.4)
'BabelScheduler' with instanceId 'okinawa1315316176852'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 25 threads.
  Using job-store 'org.quartz.impl.jdbcjobstore.JobStoreTX' - which supports
persistence. and is clustered.

[INFO] impl.StdSchedulerFactory Quartz scheduler 'BabelScheduler'
initialized from an externally provided properties instance.
[INFO] impl.StdSchedulerFactory Quartz scheduler version: 1.8.4
[INFO] quartz.QuartzComponent Starting Quartz scheduler: BabelScheduler
[INFO] jdbcjobstore.JobStoreTX ClusterManager: detected 1 failed or
restarted instances.
[INFO] jdbcjobstore.JobStoreTX ClusterManager: Scanning for instance
"okinawa1315315888193"'s failed in-progress jobs.
[INFO] core.QuartzScheduler Scheduler BabelScheduler_$_okinawa1315316176852
[INFO] jdbcjobstore.JobStoreTX Handling 1 trigger(s) that missed their
scheduled fire-time.

I also do find the loaded job on quartz scheduler, nothing to note here,
expect that the job is not 'durable'. Is this important ?
( seems down)

Has anyone any tips about this ? Thanks in advance !

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message