[ https://issues.apache.org/jira/browse/CAMEL-16563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337190#comment-17337190 ]
rabee commented on CAMEL-16563: ------------------------------- Thank you for your kind reply, since I use sftp endpoint when I add deleteJob=false, the application fails to start since this property is not in sftp endpoint, I added it like this but still doesn't work {code:java} @Bean QuartzComponent quartzComponent(CamelContext camelContext, SchedulerFactoryBean schedulerFactoryBean) { QuartzComponent quartzComponent = camelContext.getComponent("quartz2", QuartzComponent.class); quartzComponent.setScheduler(schedulerFactoryBean.getScheduler()); Properties properties = new Properties(); properties.getProperty("deleteJob","false") quartzComponent.setProperties(properties); return quartzComponent; } {code} I also followed your suggestion to use the latest camel and camel-quartz, but still the same behavior. am I setting the property in the incorrect place? I mean {code:java} Properties properties = new Properties(); properties.getProperty("deleteJob","false") quartzComponent.setProperties(properties); {code} > Quartz2 Cron triggers are removed upon one of the services shutdown > -------------------------------------------------------------------- > > Key: CAMEL-16563 > URL: https://issues.apache.org/jira/browse/CAMEL-16563 > Project: Camel > Issue Type: Bug > Components: camel-quartz2 > Affects Versions: 2.25.1 > Reporter: rabee > Priority: Minor > > Dear All, > I'm using camel quartz to connect to ftp (cron based job), so the job is > created on (quartz job_details, quartz_trigger, and cron_quartz_trigger) > tables, do everything is working normally, but if one of the services > shutdown then all this information got removed, and the job will not pull > files from FTP > > here is my connection url > +sftp://user@xxx:2222/path?useUserKnownHostsFile=true&scheduler=quartz2&scheduler.triggerId=some-trigger-id&scheduler.cron=0/15+*+*+?+*+*+*+ > > The scenario of removing the trigger only happens for cron jobs and is not > happening for a simple job, is there any way to stop removing this trigger > upon the shutdown of the service > (since my services are clustered and contain multiple replicas from ) -- This message was sent by Atlassian Jira (v8.3.4#803005)