I spent a day trying to figure this out with no luck. I re-read the threading chapter in Camel in Action book, but could not find how to multi-thread vm:// or seda:// routes. Perhaps I need to go back to using direct:// with some threading option. I just don't know.
I tried using: vm:// seda:// ?concurrentConsumers=3 threadPools threadPoolProfile camel:inOut vs camel:to camel:outOnly I tried reducing my route: <camel:route> <camel:from uri="seda://handle.event?concurrentConsumers=3" /> <camel:inOnly uri="seda://eventDataLogger?concurrentConsumers=3"/> But still NOTHING works. The very first message is STUCK in the first endpoint and 30 seconds later I get a the OUT message was not received. Using direct:// works great, it feels that simply replacing direct with vm:// should work equally as well, but it just gets stuck on the first endpoint. I am sure it's working for everyone else here, and this seems so basic, so why am I not getting it? Any help, would be so greatly appreciated. Thanks. -AP_ -- View this message in context: http://camel.465427.n5.nabble.com/org-apache-camel-ExchangeTimedOutException-The-OUT-message-was-not-received-within-30000-millis-tp5766508p5766527.html Sent from the Camel - Users mailing list archive at Nabble.com.