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

camel-quartz2 - When clustering, triggers may be left in a paused and unrecoverable state

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.12.4, 2.13.1, 2.14.0
    • Component/s: camel-quartz2
    • Labels:
      None
    • Environment:

      camel-quartz2, 2.13-SNAPSHOT clustered on Oracle database

    • Estimated Complexity:
      Unknown

      Description

      The reason seems to be that onConsumerStop() is called when camel is shut down. This method does not take clustering into account and pauses the trigger in the quartz database, leaving it in a state that is unrecoverable from camel. I was able to prevent this by removing pauseTrigger() from onConsumerStop(), but I'm not sure what the correct procedure should be. It seems to me like onConsumerStop() and doStop() has some overlap.

        Attachments

          Activity

            People

            • Assignee:
              njiang Willem Jiang
              Reporter:
              klodrik Arne M. Størksen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: