You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2019/05/22 08:37:00 UTC
[jira] [Assigned] (CAMEL-13476)
QuartzScheduledPollConsumerScheduler should not remove trigger when quartz
is clustered
[ https://issues.apache.org/jira/browse/CAMEL-13476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-13476:
-----------------------------------
Assignee: Claus Ibsen
> 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
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.0.0, 3.0.0-M3, 2.23.3, 2.24.1, 2.25.0
>
>
> 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)