[
https://issues.apache.org/jira/browse/CAMEL-13476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845674#comment-16845674
]
Claus Ibsen commented on CAMEL-13476:
-------------------------------------
Okay so clustering was not supported in the sense it would as you say remove
the jobs on stopping. Adding the option deleteJob which you can set to
true|false (true by default) and has check for clustering like the regular
component.
> QuartzScheduledPollConsumerScheduler should not remove trigger when quartz is
> clustered
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-13476
> URL: https://issues.apache.org/jira/browse/CAMEL-13476
> Project: Camel
> Issue Type: Improvement
> Components: camel-quartz2
> Reporter: Mark You
> Priority: Major
>
> When using ftp component with quartz scheduler, like following sample
> "ftp:"+sftpUsername+"@"+sftpHost+":"+sftpPort+"/3G?password="+sftpPw+"&binary=true&delay=5s&delete=true&scheduler=quartz2&scheduler.cron=\{{cron.3G.processing}}&scheduler.triggerId=3G_Trigger"
>
> During shutdown, camel will remove all triggers without check quartz is
> running in cluster mode or not. Since we config quartz is cluster means there
> can be other instances running, so does it make sense we should check quartz
> cluster state to decide triggers should remove or keep?
>
> !QuartzScheduledPollConsumerScheduler.java — camel-quartz2 2019-05-02
> 15-46-49.jpg!
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
