Breadcrumid not unique

Hello, I am running Camel 2.11 under websphere 7 on solaris and it looks like several incoming message are getting the same breadcrumId, is there any known bug around this ? all message are coming in trough different Mqseries JMS queues, so endpoints are differents, same breadcrum is even shared b

Re: Is there a clean way to default route transaction mode at the route builder level

Hi, Here is the solution I found, which seems to work ... in a class which extends RouteBuilder : @Override public RoutesDefinition configureRoutes(ModelCamelContext context) throws Exception { super.configureRoutes(context);

Re: Handling ConnectException at route startup

Ok I catch the point, we do have the same behaviour in our implementation, which is not a good news at all ... I guess the application server, if any in this case, catch the exception, in our case we are runing under websphere and the error appears in the websphere log, but not is not catch by our

Re: Handling ConnectException at route startup

Hi, what if you declare a general handling in a super class like : public abstract class CommonHandler extends RouteBuilder { @Override public void configure() throws Exception { // default Technical Exception handling onException(Exception.class)

Is there a clean way to default route transaction mode at the route builder level

Hello, in our current implementation, in camel 2.11, transaction mode is set globally inside a class which extend routebuilder, inside the interceptFrom() method. Since camel 2.12 onwards, this seems not to be tolerated anymore due to the fact that when switching the transaction mode the route is