You say "Every now and then, I get the following warning in my logs...
WARN - DirectProducer - No consumers available on endpoint: Endpoint[direct://Decoder]" This wouldn't happen to coincide with your timer would it? Does the polling consumer ever succeed or does it always give the no consumers error? On Mon, Mar 8, 2010 at 3:38 PM, boday <[email protected]> wrote: > > sorry, the '::' was a typo in my post only... > > the route works fine during normal execution...basically the following > > from('activemq:inbound') > .to('direct:decode'); > > from('direct:decode') > .convertBodyTo(DOMSource.class) > .process(new DecodeProcessor()) > .process(new ValidateProcessor()) > .process(new PersistProcessor()); > > I'm using a single Camel context and have 50 MaxConcurrentConsumers set on > the AMQ component. I'm doing high volume (~200 msg/s) message processing. > > My polling consumer routes traffic to the 'direct:decode' endpoint so it > will get processed immediately (rather than going to the 'inbound' queue). > It seems like this might be the issue in that both the inbound queue route > and my polling consumer are competing for the same 'direct:decode' > consumers?? > > > > ----- > Ben - Senior Consultant > using SMX 3.3.1/Camel 2.1 > -- > View this message in context: > http://old.nabble.com/DirectProducer---no-consumers-available-on-endpoint...message-is-lost-tp27828628p27829374.html > Sent from the Camel - Users mailing list archive at Nabble.com. > >
