Hi,
I see the point of making it per route and not per exchange. However, my
current use case is:
1 - I need to process a directory of large files (CSV)
2 - Each file is processed as a batch
3 - Need to process up to 3 files in parallel (using .threads(3) after the
file consumer).
4- Split each
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
The executorService of Splitter is set when splitter definition creates the
processor.
So the exectorService per Splitter processor not per each exchange.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
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
