Re: Quartz clustering in camel spring DSL - JIRA CAMEL-8076
amp;
> jobKey.getGroup().equals(checkTriggerKey.getGroup())&&jobKey.getName().equals(checkTriggerKey.getName(
>
> {*
> return quartzEndpoint;
> }
> }
> }
> return quartzEndpoint;
> }
>
>
> Except the triggerKey remaning all jobdetails are same in the existing
> quartzEndpoint so we put the condition check to return the existing quartz
> endpoint instead creating new quartz endpoint in the recoveryflow.
>
> * Summary :*
> The problem we found is while creating new quartz endpoint the
> consumerLoadBalancer is null.
>
> Please let us know the right way to get the consumerLoadBalancer values
> while creating new quartz endpoint in case of recovery flow.
>
> Thanks,
> selva
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Quartz-clustering-in-camel-spring-DSL-JIRA-CAMEL-8076-tp5759589p5759928.html
>
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: Quartz clustering in camel spring DSL - JIRA CAMEL-8076
Thanks, selva -- View this message in context: http://camel.465427.n5.nabble.com/Quartz-clustering-in-camel-spring-DSL-JIRA-CAMEL-8076-tp5759589p5759928.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Quartz clustering in camel spring DSL - JIRA CAMEL-8076
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 Camel - Users mailing list archive at Nabble.com.
Re: Quartz clustering in camel spring DSL - JIRA CAMEL-8076
b trigger details in > *qrtz_triggers* table above question, TRIGGER_TYPE is SIMPLE, but we defined > in our route is CRON type*. > > Please refer the section "*Captured in qrtz_triggers table*" in above > question. > > I think the problem is CRON type, Recovery Job Tigger type should be CRON > right? > > > Thanks, > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Quartz-clustering-in-camel-spring-DSL-JIRA-CAMEL-8076-tp5759589p5759614.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
Re: Quartz clustering in camel spring DSL - JIRA CAMEL-8076
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 defined
in sub route.
//calling sub rout
here.
...
My cluster configuration:
I have followed below Link to set up Clustering with the JDBC-Jobstore.
http://www.quartz-scheduler.org/documentation/quartz-2.x/configuration/ConfigJDBCJobStoreClustering
I have quartz.properties file in resource folder like
org/quartz/quartz.properties.
org.quartz.scheduler.instanceName = ClusteredScheduler
org.quartz.scheduler.instanceId = AUTO
org.quartz.jobStore.isClustered = true
...
org.quartz.plugin.triggerHistory.class=org.quartz.plugins.history.LoggingTriggerHistoryPlugin
org.quartz.plugin.triggerHistory.triggerFiredMessage=Trigger [{1}.{0}] fired
job [{6}.{5}] scheduled at: {2, date, dd-MM- HH:mm:ss.SSS}, next
scheduled at: {3, date, dd-MM- HH:mm:ss.SSS}
org.quartz.plugin.triggerHistory.triggerCompleteMessage=Trigger [{1}.{0}]
completed firing job [{6}.{5}] with resulting trigger instruction code: {9}.
Next scheduled at: {3, date, dd-MM- HH:mm:ss.SSS}
org.quartz.plugin.triggerHistory.triggerMisfiredMessage=Trigger [{1}.{0}]
misfired job [{6}.{5}]. Should have fired at: {3, date, dd-MM-
HH:mm:ss.SSS}
org.quartz.plugin.jobHistory.class=org.quartz.plugins.history.LoggingJobHistoryPlugin
org.quartz.plugin.jobHistory.jobToBeFiredMessage=Job [{1}.{0}] to be fired
by trigger [{4}.{3}], re-fire: {7}
org.quartz.plugin.jobHistory.jobSuccessMessage=Job [{1}.{0}] execution
complete and reports: {8}
org.quartz.plugin.jobHistory.jobFailedMessage=Job [{1}.{0}] execution failed
with exception: {8}
org.quartz.plugin.jobHistory.jobWasVetoedMessage=Job [{1}.{0}] was vetoed.
It was to be fired by trigger [{4}.{3}] at: {2, date, dd-MM-
HH:mm:ss.SSS}
QueryBuilderProcessor.java
public void process(Exchange exchange) throws Exception {
LOGGER.info("Started");
System.out.println(processor started**");
Thread.sleep(1);
System.out.println(processor Ends**);
}
Test case:
I am running the same camel application as standalone using
org.apache.camel.spring.Main class in two eclipse instance in same machine,
So by default clock is sync.
Two Node:
1. Eclipse Instance 1:(Node1) First I am starting application from eclipse
instance 1 , based on quartz properties file Quartz tables arepopulated
with the job details.
2.Eclipse Instance 2:(Node2) I am starting same application from eclipse
instance 2.
Both instance are started and could see their scheduler entries (Node1 &
Node2) in qrtz_scheduler_state table.
Stopping Job:
Constantly I watching the TRIGGER_STATE column of job in *qrtz_triggers*
table & console for two camel application.
step1 : Initially Trigger state will be "WAITING"
stept2: Once the Trigger state changed to "AQUIRED" , I go back to console
find the which node picked the job.
step3: Assume processor started**" printed from
QueryBuilderProcessor.java(Node1) and Immediately terminate the Node1 by
clicking terminate button in eclipse.
step4: Now current TRIGGER state is "BLOCKED".
step5: I could see the recovery logs in Node2 console.(Which is mentioned in
the above question).
*My doubt is , if you see the Recovering job trigger details in
*qrtz_triggers* table above question, TRIGGER_TYPE is SIMPLE, but we defined
in our route is CRON type*.
Please refer the section "*Captured in qrtz_triggers table*" in above
question.
I think the problem is CRON type, Recovery Job Tigger type should be CRON
right?
Thanks,
--
View this message in context:
http://camel.465427.n5.nabble.com/Quartz-clustering-in-camel-spring-DSL-JIRA-CAMEL-8076-tp5759589p5759614.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Quartz clustering in camel spring DSL - JIRA CAMEL-8076
er-2] INFO LoggingTriggerHistoryPlugin > - Trigger [cluster.quartz] completed firing job [cluster.quartz] with > resulting trigger instruction code: DO NOTHING. Next scheduled at: > 25-11-2014 12:36:00.000 > > > Captured in qrtz_triggers table: > > 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 quartZ cluster 141690564 > 141690540 5 CRON WAITING > > > Question: > 1.In recovery scenario QueryBuilderProcessor bean is not getting called from > quartz endpoint but in next interval QueryBuilderProcessor bean is getting > called . Did I miss anything here? > > *jar downloaded from below link:* > http://repository.apache.org/content/groups/snapshots/org/apache/camel/camel-quartz2/2.14.1-SNAPSHOT/ > > > > Please correct me If I did any mistake. > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Quartz-clustering-in-camel-spring-DSL-JIRA-CAMEL-8076-tp5759589.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
Quartz clustering in camel spring DSL - JIRA CAMEL-8076
Hi Willem, I have tested with camel 2.14.1-SNAPSHOT and the exception is gone but QueryBuilderProcessor is not getting called from quartz end point. Please find below configuration and logging information for both recovery and success scenario. In success scenario QueryBuilderProcessor is getting called from quartz endpoint and able see some system.out.printl statement in success case but its failing in recovery case. Please help me to solve this issue. Route Configuration: //calling sub rout here. ... Please find the below logs for Calling QueryBuilderProcessor from quartz endpoint: = Case 1 : //Logs for Immediate recovery : failure with recovery --- 2014-11-25 12:28:47,319 [_ClusterManager] INFO JobStoreTX - ClusterManager: detected 1 failed or restarted instances. 2014-11-25 12:28:47,319 [_ClusterManager] INFO JobStoreTX - ClusterManager: Scanning for instance "16898502964"'s failed in-progress jobs. 2014-11-25 12:28:56,675 [_ClusterManager] INFO JobStoreTX - ClusterManager: ..Scheduled 1 recoverable job(s) for recovery. 2014-11-25 12:29:08,599 [ontext_Worker-1] INFO LoggingTriggerHistoryPlugin - Trigger [RECOVERING_JOBS.recover_16898502964_1416898727319] fired job [cluster.quartz] scheduled at: 25-11-2014 12:28:00.000, next scheduled at: null 2014-11-25 12:29:08,600 [ontext_Worker-1] INFO LoggingJobHistoryPlugin - Job [cluster.quartz] to be fired by trigger [RECOVERING_JOBS.recover_16898502964_1416898727319], re-fire: 0 2014-11-25 12:29:08,604 [ontext_Worker-1] WARN CamelJob - Cannot find existing QuartzEndpoint with uri: quartz2://cluster/quartz?cron=0+0%2F4+*+*+*+%3F&recoverableJob=true&stateful=true. Creating new endpoint instance. 2014-11-25 12:29:09,514 [ontext_Worker-1] INFO QuartzEndpoint - Job cluster.quartz (triggerType=CronTriggerImpl, jobClass=StatefulCamelJob) is scheduled. Next fire date is null 2014-11-25 12:29:09,526 [ontext_Worker-1] INFO LoggingJobHistoryPlugin - Job [cluster.quartz] execution complete and reports: null 2014-11-25 12:29:09,528 [ontext_Worker-1] INFO LoggingTriggerHistoryPlugin - Trigger [RECOVERING_JOBS.recover_16898502964_1416898727319] completed firing job [cluster.quartz] with resulting trigger instruction code: DELETE TRIGGER. Next scheduled at: null case 2: //Normal flow : success --- 2014-11-25 12:32:04,901 [ontext_Worker-2] INFO LoggingTriggerHistoryPlugin - Trigger [cluster.quartz] fired job [cluster.quartz] scheduled at: 25-11-2014 12:32:00.000, next scheduled at: 25-11-2014 12:36:00.000 2014-11-25 12:32:04,902 [ontext_Worker-2] INFO LoggingJobHistoryPlugin - Job [cluster.quartz] to be fired by trigger [cluster.quartz], re-fire: 0 2014-11-25 12:32:04,958 [ontext_Worker-2] INFO QueryBuilderProcessor - Started processor started**//system.out line from QueryBuilderProcessor processor Ends** 2014-11-25 12:32:16,658 [ontext_Worker-2] INFO LoggingJobHistoryPlugin - Job [cluster.quartz] execution complete and reports: null 2014-11-25 12:32:16,658 [ontext_Worker-2] INFO LoggingTriggerHistoryPlugin - Trigger [cluster.quartz] completed firing job [cluster.quartz] with resulting trigger instruction code: DO NOTHING. Next scheduled at: 25-11-2014 12:36:00.000 Captured in qrtz_triggers table: S.NO. TRIGGER_GROUP JOB_NAME JOB_GROUP NEXT_FIRE_TIME PREV_FIRE_TIME PRIORITY TRIGGER_STATE TRIGGER_TYPE 1. RECOVERING_JOBSquartzcluster141690540 -1 5SIMPLEWAITING 2. clusterquartZcluster141690564 141690540 5CRON WAITING Question: 1.In recovery scenario QueryBuilderProcessor bean is not getting called from quartz endpoint but in next interval QueryBuilderProcessor bean is getting called . Did I miss anything here? *jar downloaded from below link:* http://repository.apache.org/content/groups/snapshots/org/apache/camel/camel-quartz2/2.14.1-SNAPSHOT/ Please correct me If I did any mistake. -- View this message in context: http://camel.465427.n5.nabble.com/Quartz-clustering-in-camel-spring-DSL-JIRA-CAMEL-8076-tp5759589.html Sent from the Camel - Users mailing list archive at Nabble.com.
