camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: startupOrder() on a route
Date Mon, 13 Jun 2011 08:29:19 GMT
On Fri, Jun 10, 2011 at 9:53 PM, bvahdat <> wrote:
> Somehow I still don't get it right, but maybe it's because of my poor english
> Let's consider the example you mentioned with A and B and equate them with
> the example in the book (page 416). In this case A would be the route with
> the Id "webservice" and B would be the one with the Id "update". Now as you
> already said:
> So if A takes in messages, but to process those messages its dependent on B
> and C. Then we need to stop A from taking in new messages. But the existing
> messages should allow to process and use B and C.
> I exactly agree on that! So the shutdown order should be first A and then B,
> that's "webservice" and THEN "update". But as you mention on page 426 the
> "update" route is the first which get's shutdown as the first route  before
> the route with the Id "webservice" which was effectively dependent on
> "update" . So why the warnings:
> WARN - DirectProducer  - No consumer available on endpoint:
> Endpoint[direct://update] to process...

If you read further on page 427 there is a TIP telling you how Camel
2.5 was improved, and handles this example out of the box.
But you may have use-cases where the shutdown is more complicated, and
you need to configure the ordering / defer etc.

> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message