Re: camel 2.11.0 file move/moveFailed error, but 2.10.4 works fine
Hi, Just give updates, after I tried the latest 2.11.1, it works fine. Can someone tell me the reason what happened in 2.11.0? I am curious to the details. -- View this message in context: http://camel.465427.n5.nabble.com/camel-2-11-0-file-move-moveFailed-error-but-2-10-4-works-fine-tp5737743p5737744.html Sent from the Camel - Users mailing list archive at Nabble.com.
camel 2.11.0 file move/moveFailed error, but 2.10.4 works fine
I have a file: component like below file.trigger.directory=trigger file.trigger.error.directory=.error file.trigger.done.directory=.done when I use 2.11.0. when the route has exception, it throws below exception: 2013-08-22 17:07:39 WARN GenericFileOnCompletion:136 - Caused by: [org.apache.camel.component.file.GenericFileOperationFailedException - Cannot create directory: trigger\.error\name-now:MMdd_HHmmss (could be because of denied permissions)] org.apache.camel.component.file.GenericFileOperationFailedException: Cannot create directory: trigger\.error\name-now:MMdd_HHmmss (could be because of denied permissions) at org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:106) at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.rollback(GenericFileRenameProcessStrategy.java:67) at org.apache.camel.component.file.GenericFileOnCompletion.processStrategyRollback(GenericFileOnCompletion.java:164) at org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:88) at org.apache.camel.component.file.GenericFileOnCompletion.onFailure(GenericFileOnCompletion.java:57) at org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:52) at org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:226) at org.apache.camel.processor.UnitOfWorkProcessor.doneUow(UnitOfWorkProcessor.java:199) at org.apache.camel.processor.UnitOfWorkProcessor.access$000(UnitOfWorkProcessor.java:37) at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:157) at org.apache.camel.processor.RouteContextProcessor$1.done(RouteContextProcessor.java:56) at org.apache.camel.processor.RouteContextProcessor$1.done(RouteContextProcessor.java:56) at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:81) at org.apache.camel.processor.MulticastProcessor.doDone(MulticastProcessor.java:753) at org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:232) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.BacklogTracerInterceptor.process(BacklogTracerInterceptor.java:84) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:46) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:335) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:46) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117) at org.apache.camel.processor.RouteInflightRepositoryProcessor.processNext(RouteInflightRepositoryProcessor.java:48) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72) at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:350) at org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:197) at o
Re: Add thread pool configuration for SEDA using xml
Hi Claus, Thanks for your reply. So can we conclude, if we use xml configuration for seda, we can't have a thread pool which can increase/shrink dynamically at runtime, is that right? Thanks. Billy -- View this message in context: http://camel.465427.n5.nabble.com/Add-thread-pool-configuration-for-SEDA-using-xml-tp5716324p5716494.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Add thread pool configuration for SEDA using xml
Hi William,
Thanks for your reply.
Maybe I didn't describe my question clearly.
>From seda spec, it says "As for the difference between the two (Concurrent
consumers and thread pool), note a thread pool can increase/shrink
dynamically at runtime depending on load, whereas the number of concurrent
consumers is always fixed."
and we can use "from("seda:stageName").thread(5).process(...)" to configure
the thread pool for seda via DSL, so I think using DSL can make seda threads
number increase/shrink dynamically, which means it doesn't have to always be
5 concurrent consumers.
However, if you use xml, I only we can configure concurrentConsumers which
has fixed number threads (e.g. always 5 concurrent consumers), but I don't
know how to make the same effect using xml as DSL
"from("seda:stageName").thread(5).process(...)". Can someone shed some light
on this?
--
View this message in context:
http://camel.465427.n5.nabble.com/Add-thread-pool-configuration-for-SEDA-using-xml-tp5716324p5716536.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Add thread pool configuration for SEDA using xml
Hi, from http://camel.apache.org/seda.html, we can use DSL to add thread pool
to SEDA, e.g. from("seda:stageName").thread(5).process(...),
can anyone tell me how to do the same thing using xml?
I have a xml seda route definition.
Thanks a lot.
Billy
--
View this message in context:
http://camel.465427.n5.nabble.com/Add-thread-pool-configuration-for-SEDA-using-xml-tp5716324.html
Sent from the Camel - Users mailing list archive at Nabble.com.
