Hi, Can you specify the camel context name in your cluster environment?
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On October 20, 2014 at 12:01:04 PM, lakshmi.prashant (lakshmi.prash...@gmail.com) wrote: > Hi, > > We get many misfires, while quartz is working in clustered mode. > > This is when the trigger is acquired / executed on another VM than the > one that inserted the job data: > > We get an error while is CamelJob in that VM gets executed for a trigger. > The camel job tries to locate the camel context & the route, by looking up > using the QUARTZ_CAMEL_CONTEXT_NAME in the Quartz schedulerContext. > > No CamelContext could be found with name: *572-Quartz2_Mig_Test1* > at > org.apache.camel.component.quartz2.CamelJob.getCamelContext(CamelJob.java:77) > > at > org.apache.camel.component.quartz2.CamelJob.execute(CamelJob.java:48) > at org.quartz.core.JobRunShell.run(JobRunShell.java:202) > at > org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) > > > I think that the QUARTZ_CAMEL_CONTEXT_NAME is stored by the QuartzComponent > using the DefaultManagementNameStrategy & stored while creating the Quartz > schedulerContext & this also gets set in the Job datamap. > > The prefix of the camelcontext name is generated using a counter and may not > be the same in all VM's. > Hence, if any other VM in the cluster gets the trigger callback to execute > the CamelJob, it throws the above error. > > Is this a known issue - can someone kindly tell me how to get this resolved? > > Thanks, > Lakshmi > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508p5757783.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
