Hi
Can you not just reorder the routes? Camel should process them in the
order they are defined.
On Mon, Apr 20, 2009 at 10:50 AM, Henric Hedin <hhe...@gmail.com> wrote:
> Hi,
>
> I have a problem which occurs when I have a Route which looks like this:
>
> // 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("validtor:foo.xsd")
> .to("jms:queue:DEST_QUEUE");
>
>
> Everything works fine when everything is initiated/started, but if there
> already is a message on the JMS-source when camel is started I get the
> following error:
>
> WARN DirectProducer - No consumers available on endpoint:
> Endpoint[direct:processMsg] to process Exchange[JmsMessage:
>
> Seems like my "Main Flow" (defined in the same
> RouteBuilder.configure-method) isn't fully initiated/started when "initiated
> from JMS" is already up and running (and starts to consume messages). Could
> this be handled in some way, i.e. to not start to consume messages before
> all Route's are fully started?
>
> Right now I am using Spring to start my routes (inside a
> META-INF/spring/camel-context.xml) and I'm using Camel 2.0-M1.
>
> Best Regards,
> Henric
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
