Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-13476

QuartzScheduledPollConsumerScheduler should not remove trigger when quartz is clustered

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Unknown

    Description

      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?

       

       

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            davsclaus Claus Ibsen
            bonbonmark Mark You
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment