On Mon, Jan 20, 2014 at 3:04 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > The executorService of Splitter is set when splitter definition creates the > processor. > So the exectorService per Splitter processor not per each exchange. >
Correct, and also remember that executorService = thread pool. And each splitted exchange uses its own thread from the thread pool (borrow it / return it when done). This is the normal use-cases for thread pools. > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) > (English) > http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On January 20, 2014 at 5:21:11 AM, hshicx (hs-...@hicxsolutions.com) wrote: >> >> Hi, >> >> I am wondering if the executorService (configured using execuotServiceRef) >> is shared among the different Exchanges being split using the >> same route. I >> am aware that execuotServiceRef will look up for a >> *ThreadPoolProfileSupport* in the Registry if an exectorService >> with the >> same id is not found in the regisrty and create a new executorService. >> I am >> not sure about the behavior of the ThreadPoolProfileSupport >> however. Does >> it create a new executorService for each Exchange being split >> (which what I >> want) or one executorService per route which is then shared by >> all >> Exchanges? >> >> Thanks a lot, >> Hs >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Splitter-with-parallelProcessing-and-exectorService-for-each-Exchange-being-split-tp5746223.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
