Route with same routeId killing previous route

[jamie3_james.archibald]

I have a custom camel component for a pub/sub system which is defined in a routers as follows:

class Router extends RouteBuilder() {

   from("customComponent:foo")

      .routeId("My Consumer")

      .to("log:${body}");

}

I'm creating two instances of the Router and adding them to the camel context. For some reason the second one seems to kill the first one. And by "kill" I mean when messages are received at "customComponent:foo" only the second router receives the message.

main() {

   context.addRoutes(new Router());

   context.addRoutes(new Router());

}

Examining the camel logs didn't reveal anything. Before I get into examining the camel code I'm wondering if this is by design or a possible a bug?

[davsclaus]

The routeId must be unique. I guess we should add a better early duplicate detection.

I added a ticket to track this

http://fusesource.com/issues/browse/MR-617

[davsclaus]

When you add a route with a id, that already exists, then the old route is stopped and removed. So that is why the route seems like killed.

This is by design, as it allows to easy upgrade routes.

So I am not sure if the duplicate check is a good idea.

[jamie3_james.archibald]

Ok, good to know. I checked the javadoc for the routeId() function and it didn't indicate any possible problems when setting duplicate ids.

Perhaps a simple log warning in camel would be great.

thanks again for the reply.

Edited by: jamie3 on May 24, 2012 10:47 AM

[davsclaus]

A good idea. I have added javadoc to the route id, and other parts on CamelContext to highlight this.