camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-1556) Controlling initiatation order of routes
Date Sat, 03 Oct 2009 18:28:00 GMT


Claus Ibsen commented on CAMEL-1556:

BTW We also improved in Camel 2.1 to start the inputs to the routes at the very end. So the
initial problem will without this patch be hard to reproduce as Camel starts all the inputs
very fast at the same time.

> Controlling initiatation order of routes
> ----------------------------------------
>                 Key: CAMEL-1556
>                 URL:
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Henric Hedin
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
> Would be nice if it was possible to control the order of how routes are initiated. If
the following code is implemented within the same RouteBuilder.configure:
> // initiated from queue
> from("jms:queue:SOURCE_QUEUE").
> to("direct:processMsg");
> // initiated from file
> from("file://inbox).
> to("direct:processMsg");
> // Main flow
> from("direct:processMsg")
>  .process("...")
>  .to("validator:foo.xsd")
>  .to("jms:queue:DEST_QUEUE");
> ... and there already is a message waiting on the JMS-source when camel is started, it
could/will lead to the following error:
>  WARN  DirectProducer                 - No consumers available on endpoint: Endpoint[direct:processMsg]
to process Exchange[JmsMessage:
>  Today the are workarounds (by splitting in multiple files, and re-order route definitions),
but maybe this could solved in some other better way (which also could affect a graceful shutdown).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message