camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <willem.ji...@gmail.com>
Subject Re: Message blocks route until all redelivery attempts are exhausted
Date Sat, 03 Apr 2010 02:10:45 GMT
Hi,

Can you try to add this option "concurrentConsumers=5" into the seda 
endpoint's URI?
By default there is only one thread to consumer the message in the queue.

Willem

Dragisa Krsmanovic wrote:
> I have a route that is configured to re-deliver messages on exception.
> If there are messages in that queue and one of them fails, all other
> messages are blocked until all re-delivery attempts are exhausted.
> 
> I would like other messages to go through while the ones that failed are
> waiting for their re-delivery. Message order is not important. What is a
> good way to do this ?
> 
> 
> The route I tested with looks like this:
> 
> from("seda:start")
>  .onException(Exception.class)
>    .handled(true)
>    .redeliverDelay(100)
>    .maximumRedeliveries(1)
>    .to("mock:error")
>  .end()
>  .process(new TestProcessor())
>  .to("mock:end");
> 
> 
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> This email is confidential to the intended recipient. If you have received it in error,
please notify the sender and delete it from your
> system. Any unauthorized use, disclosure or copying is not permitted. The views or opinions
presented are solely those of the sender and do
> not necessarily represent those of Public Library of Science unless otherwise specifically
stated. Please note that neither Public Library
> of Science nor any of its agents accept any responsibility for any viruses that may be
contained in this e-mail or its attachments and it
> is your responsibility to scan the e-mail and attachments (if any).
> 


Mime
View raw message