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

Quartz - ExchangesCompleted increment without messages to process

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Not A Bug
    • 3.20.8
    • None
    • camel-quartz
    • None
    • Unknown

    Description

      I have the following route running on Camel3 (3.20.8), and I'm experience some ExchangesCompleted increment each time the routine runs (quartz), even when there's no messages to process.

      On Camel2 (2.23.4), with the same route structure, I don't see the increment when there's no processing messages.

      Do you know if quartz component on Camel3, may trigger a Camel route even if there are no messages to process?

      <route id="e4282f9d-f0be-4dbd-93ec-9eef9b2aae0b_throttling">
        <from uri="quartz://e4282f9d-f0be-4dbd-93ec-9eef9b2aae0b_timer?trigger.repeatCount=-1&amp;trigger.repeatInterval=2000&amp;trigger.timeZone=Europe/Amsterdam"/>
        <setProperty propertyName="AssimblyQueueName">
          <constant>ID_6581d1205827223f1f00000e_test_e4282f9d-f0be-4dbd-93ec-9eef9b2aae0b_throttling</constant>
        </setProperty>
        <process ref="QueueMessageChecker"/>
        <filter>
          <simple>${exchangeProperty.AssimblyQueueHasMessages} == true</simple>
          <log message="Inside first filter"/>
          <loop copy="true">
            <log message="Inside loop"/>
            <constant>1</constant>
            <setProperty propertyName="Enrich-Type">
              <simple>application/override</simple>
            </setProperty>
            <setProperty propertyName="AssimblyAggregateNoExceptionOnNull">
              <simple resultType="java.lang.Boolean">true</simple>
            </setProperty>
            <pollEnrich strategyRef="CurrentEnrichStrategy" timeout="5000">
              <constant>activemq:ID_6581d1205827223f1f00000e_test_e4282f9d-f0be-4dbd-93ec-9eef9b2aae0b_throttling</constant>
            </pollEnrich>
            <filter>
              <simple>${body} != null</simple>
              <log message="Inside second filter"/>
              <removeHeaders pattern="fireTime|jobRunTime|nextFireTime|previousFireTime|refireCount|scheduledFireTime|triggerGroup|triggerName|jobDetail|jobInstance|mergedJobDataMap|result|scheduler|trigger" excludePattern="breadcrumbId"/>
              <to uri="direct-vm:ID_6581d1205827223f1f00000e_test_e4282f9d-f0be-4dbd-93ec-9eef9b2aae0b?exchangePattern=InOnly"/>
            </filter>
          </loop>
        </filter>
      </route> 

      Attachments

        Activity

          People

            Unassigned Unassigned
            brunovg Bruno Gonçalves
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: