Hi Selva,
Thanks for sharing your patch with us. Your patch looks good to me, and I
managed to reproduce the error by doing some change in the
SpringQuartzConsumerTwoAppsClusteredRecoveryTest.
I will commit the patch shortly.
Regards,
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.co
Hi Willem,
I have downloaded(2.14.x from github) and debugged the camel quartz
component source code and found the reason for the issue i am facing.
As i already posted i am facing issue in the cluster environment, deployed
the camel application as stand alone program running 2 instances. While
e
Sorry Willem , its typo error I could not copy the row from DB so manually
formed the table format.
*quartZ* -> small 'z' i.e quartz
--
View this message in context:
http://camel.465427.n5.nabble.com/Quartz-clustering-in-camel-spring-DSL-JIRA-CAMEL-8076-tp5759589p5759639.html
Sent from the C
Did you clean up your database after testing?
S.NO. TRIGGER_GROUP JOB_NAME JOB_GROUP NEXT_FIRE_TIME PREV_FIRE_TIME
PRIORITY TRIGGER_STATE TRIGGER_TYPE
1. RECOVERING_JOBS quartz cluster 141690540 -1
5 SIMPLE WAITING
2. cluster
Hi Willem,
I have defined one quartz2 endpoint route and one sub route in
camel-context.xml file . Whenever the quartz scheduler triggers , the quartz
end point will call the sub route using direct component. I am printing some
text in console using bean processor(QueryBuilderProcessor) which is d
I did some test on my side, I cannot reproduce the error that you meet.
From the failure with recovery log that you showed, The next scheduled is null
and Camel Job cannot find the QuartzEndpoint.
2014-11-25 12:29:08,599 [ontext_Worker-1] INFO LoggingTriggerHistoryPlugin
- Trigger [RECOVERING_JO
