1 2 Previous Next 20 Replies Latest reply on Oct 15, 2012 11:47 AM by wbailey Go to original post
      • 15. Re: Camel Route Startup Issues...
        stlewis

        Just to check, does your profile inherit from the "default" profile?

        • 16. Re: Camel Route Startup Issues...
          wbailey

          Log file and console output from the list comand attached

          • 17. Re: Camel Route Startup Issues...
            wbailey

            No, it inherits from esb. Should I try default?

            • 18. Re: Camel Route Startup Issues...
              stlewis

              Should be okay, note that the "esb" profile does install an activemq broker as it inherits from "mq".  You may be able to get away with the "camel" profile, but really as long as you're in some way bringing in the "default" profile, and you are, just wanted to check.

              • 19. Re: Camel Route Startup Issues...
                iocanel

                There is also the following entry:

                 

                2012-10-15 16:05:38,053 | INFO  | NAPSHOT-thread-1 | BlueprintContainerImpl           | 10 - org.apache.aries.blueprint - 0.3.1.fuse-70-084 | Bundle com.test.sms.smpp-simulator is waiting for dependencies

                 

                If you are using the properties component in your bundle then its absolutely normal that this happens. However, that dependency should be meet as soon as the camel-core bundle gets started.

                 

                Looking deeper in the log, I see that the camel-core bundle does get started, and I also see that your camel route also gets started:

                 

                2012-10-15 16:05:38,661 | INFO  | NAPSHOT-thread-1 | SmppSimulatorBean                | 98 - com.test.sms.smpp-simulator - 1.0.0.SNAPSHOT | Starting SMPP simulator on port 3211 using SSL false

                2012-10-15 16:05:38,661 | INFO  | NAPSHOT-thread-1 | SmppSimulatorBean                | 98 - com.test.sms.smpp-simulator - 1.0.0.SNAPSHOT | started.

                2012-10-15 16:05:38,755 | INFO  | NAPSHOT-thread-1 | JettyHttpComponent               | 109 - org.apache.camel.camel-jetty - 2.9.0.fuse-70-084 | Using default Jetty continuation timeout for: Endpoint[http://0.0.0.0/sendsms]

                2012-10-15 16:05:38,786 | INFO  | NAPSHOT-thread-1 | BlueprintCamelContext            | 112 - org.apache.camel.camel-core - 2.9.0.fuse-70-084 | Route: webAction started and consuming from: Endpoint[http://0.0.0.0/sendsms]

                 

                So from what I understand there shouldn't be any problem, other than a the misleading output of osgi:list.

                • 20. Re: Camel Route Startup Issues...
                  wbailey

                  Thank you, I'll give it a go and see if it is working.

                   

                  It definitely wasn't working before adding camel-core and camel-blueprint. So that may of fixed the issue but I didn't realize as the output from list was still 'GracePeriod'.

                  1 2 Previous Next