camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco Westermann <MarWesterm...@gmx.de>
Subject bug in startup order?
Date Mon, 15 Oct 2012 07:15:13 GMT
Hi,

is there a bug with the startupOrder feature? I have the following route:

from ("activemq:a")
     .to("direct:b");

from("direct:b")
     .bean("DoSomething");

When I start my bundle with this route and the queue a already has some 
messages on it I get a warning that no consumers are available for 
direct:b. So I changed the startup order:

from ("activemq:a")
     .startupOrder(100)
     .to("direct:b");

from("direct:b")
     .startupOrder(1)
     .bean("DoSomething");

but with this I get the same error again.

It only works if I change the order of the definition like this:

from("direct:b")
     .startupOrder(1)
     .bean("DoSomething");

from ("activemq:a")
     .startupOrder(100)
     .to("direct:b");

I use camel in the actual smx release 4.4.2

regards, Marco

Mime
View raw message