The splitter sets a size as a exchange property, so you can know the
total number of entries.

See the exchange properties at
http://camel.apache.org/splitter


On Mon, Jun 22, 2015 at 7:15 AM, Andrew Block <[email protected]> wrote:
> Hello,
>
> Do you have the parallelProcessing option of the split set to true? If not, 
> it is possible messages were always processing sequentially but it is now 
> become apparent due to the request/reply nature of the route and the time it 
> takes to complete the downstream route.
>
> - Andy
>
> --
> Andrew Block
>
> On June 21, 2015 at 12:54:13 PM, jackkirsten ([email protected]) wrote:
>
> Hi, I have an index file that lists a list of file names and each file needs
> to be processed asynchronously. So I have a camel context with quartz timer
> scheduled to trigger at X time (once a day). Then within that route, I have
> a split logic to split the file name list and each file is sent to SEDA
> queue for asynchronous processing. All works well so far. Now I want to
> find out when all files got processed. So I tried this:
>
> <to uri=&quot;seda:fileProcessing?&lt;b>waitForTaskToComplete=Always*"/>
>
> With this setup, each file processing gets sequential and I lose the
> asynchronous behavior and it slows down the overall processing now. On the
> consumer side, I have set the concurrentConsumers=5 but still it behaves
> sequential.
>
> Question: If I set waitForTaskToComplete=Always in the producer side and I
> set concurrentConsumers=5, will that make the overall processing behavior
> sequential though I set concurrentConsumers > 0? It seems like
> waitForTaskToComplete takes precedence and nullfies the concurrentConsumers
> setting.
>
> How do I achieve async behavior by processing all files in parallel but I
> want to wait for all SEDA queue processing is done before I say in the
> quartz route that all processing is fully done for that execution?
>
> Please provide some thoughts.
>
> Thanks.
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/waitForTaskToComplete-concurrentConsumers-tp5768446.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: [email protected]
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Reply via email to