That's the whole route what I have posted above! It is definitely strange as I have another route that does the same thing and that route worked perfectly fine! I tried changing the names of the route id, direct constants and its values, but of no help!
What is even more strange is that I can see in the console logs that the consumer route for the Endpoint[direct://processRefDataRouter] is already started! -- View this message in context: http://camel.465427.n5.nabble.com/No-Consumer-available-Exception-tp5736133p5736143.html Sent from the Camel - Users mailing list archive at Nabble.com.
