4 Replies Latest reply on Apr 24, 2013 10:44 AM by iocanel

    Problem with the example-camel profile

    sobkowiak

      Hi

       

      I'm just testing the JBoss Fuse jboss-fuse-6.0.0.redhat-015. I have created fabric and created a new child container. Next I have choosen the profiles for my child container - camel and example-camel. After connecting the container I see 2 routes

       

      f@test> camel:route-list

      Route Id             Context Name         Status             

      [route1            ] [fabric-camel-demo ] [Started           ]

      [route2            ] [fabric-camel-demo ] [Started           ]

       

      f@test> camel:route-info route1

      Camel Route route1

              Camel Context: fabric-camel-demo

       

      Properties

                      id = route1

                      parent = 1f4e7db

       

      Statistics

              Exchanges Total: 49

              Exchanges Completed: 0

              Exchanges Failed: 49

              Min Processing Time: 0ms

              Max Processing Time: 0ms

              Mean Processing Time: 0ms

              Total Processing Time: 0ms

              Last Processing Time: 0ms

              Load Avg: 0.00, 0.00, 0.00

              First Exchange Date:

              Last Exchange Completed Date:

       

      f@test> camel:route-info route2

      Camel Route route2

              Camel Context: fabric-camel-demo

       

      Properties

                      id = route2

                      parent = 6b6dfe

       

      Statistics

              Exchanges Total: 0

              Exchanges Completed: 0

              Exchanges Failed: 0

              Min Processing Time: 0ms

              Max Processing Time: 0ms

              Mean Processing Time: 0ms

              Total Processing Time: 0ms

              Last Processing Time: 0ms

              Load Avg: 0.00, 0.00, 0.00

              First Exchange Date:

              Last Exchange Completed Date:

       

      The second route is not processing any messages produced by the first route. In the log I could find an exception (see attachment)

       

      Is this problem known already?

       

      Best regards

        • 1. Re: Problem with the example-camel profile
          sobkowiak

          Hi

           

          I think this is not the problem of the new version but I'm doing something wrong. I've tested the same scenario with Fuse ESB 7.1.0 and I have the same issue. I make following steps

           

          fabric:create

          fabric:container-create-child root broker

          fabric:container-change-profile broker mq

          fabric:container-create-child root camel

          fabric:container-change-profile camel example-camel

           

          I see also that the camel instance is not in the cluster

           

          FuseESB:karaf@root> fabric:cluster-list

          [cluster]                      [masters]                      [slaves]                       [services]

          fusemq/default                                                                              

             root                        root                           -                              tcp://172.16.123.1:53144

             broker                      broker                         -                              tcp://172.16.123.1:38883

           

          Could it cause this issue?

           

          Could somebody tell me what I am doin wrong?

          • 2. Re: Problem with the example-camel profile
            sobkowiak

            An issue for this problem has been opened http://fusesource.com/issues/browse/ENTMQ-263

            • 3. Re: Problem with the example-camel profile
              aileenc

              This issue is fixed in the GA release of JBoss Fuse 6.0 which will be available shortly.

              • 4. Re: Problem with the example-camel profile
                iocanel

                The root cause of this issue is that the credentials used in the example-camel profile do not match with the credentials of the container.

                You will need to configure the credentials of the example.