Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-7122

Camel: False for automated startup does not work

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Explained
    • jboss-fuse-6.3
    • None
    • Camel
    • None
    • Hide

      1) I have several routes in one application
      2) Routes are defined as <route autoStartup="false" id="019CurrencyR" trace="true">
      3) Deploy on Camel server

      Show
      1) I have several routes in one application 2) Routes are defined as <route autoStartup="false" id="019CurrencyR" trace="true"> 3) Deploy on Camel server

    Description

      Routes usually start despite of the settings. I am not sure if they always start or only sometimes: this is new application and if this sometimes works correctly, that is too rare occurrence.

      Example logs entries in Hawtio are on below. As you can see it detects the "do not start" setting and says nothing started. Then immediately after that it starts it anyway.

      If I pause half of the routes manually, then sometimes in next installation it does not start those that were paused (if I can trust on UI), and sometimes it starts all.

      2017-07-21 09:59:38
      INFO
      org.apache.camel.blueprint.BlueprintCamelContext
      Skipping starting of route FtpReadTestR as its configured with autoStartup=false
      2017-07-21 09:59:38
      INFO
      org.apache.camel.blueprint.BlueprintCamelContext
      Total 1 routes, of which 0 are started.
      2017-07-21 09:59:38
      INFO
      org.apache.camel.blueprint.BlueprintCamelContext
      Apache Camel 2.17.0.redhat-630187 (CamelContext: FtpReadTestC) started in 0.019 seconds

      Attachments

        Activity

          People

            cibsen@redhat.com Claus Ibsen
            timo.riikonen Timo Riikonen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: