camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: bug in startup order?
Date Mon, 22 Oct 2012 09:44:07 GMT
Hi

I added an test on trunk. And cannot reproduce the ordering issue. The
routes with the lowest startup order is started before the higher
values.
http://svn.apache.org/viewvc?rev=1400814&view=rev




On Mon, Oct 15, 2012 at 9:15 AM, Marco Westermann <MarWestermann@gmx.de> wrote:
> 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



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Mime
View raw message