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

    Problem with the example-camel profile

    Krzysztof Sobkowiak Newbie

      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