On Thu, Jun 24, 2010 at 7:29 PM, Ingo Düppe <mailing-li...@dueppe.com> wrote: > Hello, > > I found still some issues about clustering camel-quartz component (based > on the current trunk version) > > First, why are stateful triggers are unscheduled on a graceful shutdown. > I guess this causes, that the trigger is deleted within the database. So > not only the node that is shutting down loses the triggers also the > other nodes in the cluster will lost their triggers. > > Maybe checking if the trigger is stateful before removing on shutdown > will help. > > Second, see the log below. It seems that the default trigger is fired > before it is resumed. > > Any suggestions? >
I think the reason is the scheduler is started before the other routes has been fully started. And quartz starts very quick. We could add an option so you can configure a delay option so it can be started with delay. It has a startDelayed method: http://www.quartz-scheduler.org/docs/api/1.8.1/org/quartz/Scheduler.html However a better solution is to offer this as a feature in Camel which allows component to register callbacks to be invoked when all the other stuff have been started, so they can start last. I have created a ticket to track that https://issues.apache.org/activemq/browse/CAMEL-2855 -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
