On Thu, Jun 3, 2010 at 12:24 PM, Srini97 <[email protected]> wrote:
>
> If I use it below by removing threads() it is taking the messsages one by
> one even though there are concurrent consumers.
>
What JMS Broker are you using?
Normally using concurrentConsumer=5 on the JMS endpoint will have 5
threads process new messages on the JMS queue at the same time.
So something is odd/wrong on your system.
> from("jms-cif:queue:" +
> _notificationQueue+"?concurrentConsumers="+concurrentConsumersSize).
> process(processor)
> .onException(Exception.class).retryUntil(bean("myRetryBean")).end()
> .recipientList(header("recipientListHeader").tokenize(","))
> .parallelProcessing().executorService(customThreadPoolExecutor)
> .aggregationStrategy(new
> RecipientAggregationStrategy(deliveryEndpoints, _endpointDeliveredBaseUri))
> .to("direct:chunk.completed");
>
>
>
>
>
>
>
> --
> View this message in context:
> http://old.nabble.com/Getting-exception-when-using-retryUntil-with-concurrentConsumers-tp28756173p28765667.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
