I don't know what I did, but it's working now. I'll take it, but I'm not a big fan of that;)
On Wed, Aug 31, 2011 at 7:52 AM, Samuel Cox <crankydi...@gmail.com> wrote: > I'm thinking this is not what you want, but here is the declaration of my > route: > > <camel:camelContext id="camelContext"> > <camel:route> > <camel:from > uri="vm:di.services.batch?timeout=60000&concurrentConsumers=10"/> > <camel:process ref="batchEndpoint"/> > </camel:route> > </camel:camelContext> > > I have never explicitly configured the Camel context. If such a thing > exists, either Fuse is doing it for me or someone on my team is. > > On Wed, Aug 31, 2011 at 6:22 AM, Willem Jiang <willem.ji...@gmail.com> wrote: >> Can you show us the camel context configure ? >> Is there any sead consumer defined in the route ? >> >> On Wed Aug 31 18:55:47 2011, Samuel Cox wrote: >>> >>> Hi, >>> >>> We're using Camel 2.6.0 in Fuse 4.3. We have a Camel route that >>> exposes a bean method as a vm endpoint. I'm trying to test this route >>> with PaxExam 2.2.0. When I send an exchange to it, it always times >>> out. I have put breakpoints in the bean method, but they never get >>> hit. It hangs in SedaProducer.process (lock.await) until the timeout >>> occurs. Other routes with a similar configuration work fine. >>> >>> Is there anything I can do (debug, look at logs, etc.) to determine >>> why the exchange is timing out? >>> >>> Thanks. >> >> >> >> -- >> Willem >> ---------------------------------- >> FuseSource >> Web: http://www.fusesource.com >> Blog: http://willemjiang.blogspot.com (English) >> http://jnn.javaeye.com (Chinese) >> Twitter: willemjiang Weibo: willemjiang >> >
