Re: Thread pool for components in Camel

2011-11-25 Thread Claus Ibsen
On Fri, Nov 25, 2011 at 10:40 AM, diwakar wrote: > Hi, > >                In Servicemix/JBI thread pools by are there by default (at > component level). >                Why isn't the same approach taken for Camel? In Camel thread > (/async) has to be configured explicitly in the route. >        

Re: Thread pool for components in Camel

2011-11-25 Thread diwakar
Hi, In Servicemix/JBI thread pools by are there by default (at component level). Why isn't the same approach taken for Camel? In Camel thread (/async) has to be configured explicitly in the route. Please let me know your comment. With Best Regards,

Re: Thread pool for components in Camel

2011-10-14 Thread diwakar
Hi, >> Yes the file is deleted at the end, when the exchange is done. Just to understand better. Tpoller thread will read the file1, Tlogger1 will process and fwd to Twriter1 thread. Tpoller thread will read the file2, Tlogger2 will process and fwd to Twriter2 thread. . .

Re: Thread pool for components in Camel

2011-10-12 Thread Claus Ibsen
On Mon, Oct 10, 2011 at 10:36 AM, diwakar wrote: > Hi, > >           >> The file is a single threaded scheduled consumer >           Thanks for the reply. This is one difference compared to > servicemix JBI. In servicemix multiple threads can poll the input folder. >           If we use multiple t

Re: Thread pool for components in Camel

2011-10-11 Thread diwakar
Hi, >> The file is a single threaded scheduled consumer Thanks for the reply. This is one difference compared to servicemix JBI. In servicemix multiple threads can poll the input folder. If we use multiple thread only for processing, when is the file deleted? Is

Re: Thread pool for components in Camel

2011-10-10 Thread Claus Ibsen
On Sun, Oct 9, 2011 at 6:14 PM, diwakar wrote: > Hi, > >         >         >         >         >         > >        With this we can have 10 threads for the logging and the file > writing indpoints. But how to configure 10 threads for the poller > (file:input)? >        Please let me know your

Re: Thread pool for components in Camel

2011-10-09 Thread diwakar
Hi, With this we can have 10 threads for the logging and the file writing indpoints. But how to configure 10 threads for the poller (file:input)? Please let me know your comment. With Bets Regards, Diwakar -- View this message i

Re: Thread pool for components in Camel

2011-10-02 Thread diwakar
Hi, >> unless you are already use JBI a lot, and are happy with it as is. Yes, we are using JBI a lot. >> No JBI is dying/dead Yes, this is what we are concerned about. Is staying with Servicemix 3.x an option? Or should we migrate to Camel? Is c

Re: Thread pool for components in Camel

2011-10-02 Thread Claus Ibsen
On Fri, Sep 30, 2011 at 8:31 PM, diwakar wrote: > Hi, > >          Thanks for the reply. With async and defaultThreadPoolProfile, is > Camel support for parallel processing as good as Servicemix 3.x. Are there > any known limitations in Camel over JBI(Servicemix3.x). Is there any good > reason to

Re: Thread pool for components in Camel

2011-09-30 Thread diwakar
Hi, Thanks for the reply. With async and defaultThreadPoolProfile, is Camel support for parallel processing as good as Servicemix 3.x. Are there any known limitations in Camel over JBI(Servicemix3.x). Is there any good reason to use Servicemix JBI instead of Camel. Please let

Re: Thread pool for components in Camel

2011-08-21 Thread Claus Ibsen
Hi See more details here http://camel.apache.org/threading-model.html On Mon, Aug 22, 2011 at 7:14 AM, diwakar wrote: > Hi, > >         In Servicemix we can configure thread pools for components: > servicemix.corePoolSize    = 32 > servicemix.maximumPoolSize = 128 >         In camel, how can I