Mark You created CAMEL-13476:
--------------------------------
Summary: 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: Bug
Components: camel-quartz2
Reporter: Mark You
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)
