r it to work, we need to use the original message, so any changes in the
exchange while trying to process it would be ignored
--
View this message in context:
http://camel.465427.n5.nabble.com/Message-blocks-route-until-all-redelivery-attempts-are-exhausted-tp472319p5784827.html
Sent from th
very thread pool how many redeliveries you
can process concurrently. Currently its configured to allow 10 threads
in that pool. We should offer an option so you can configure this as
well. I will create a JIRA for that.
> Thx,
> Martin
> --
> View this message in context:
> http://camel.46
outes won't get worked on in parallel?
Or does this only come into effect when there's an exception?
Thx,
Martin
--
View this message in context:
http://camel.465427.n5.nabble.com/Message-blocks-route-until-all-redelivery-attempts-are-exhausted-tp472319p3371056.html
Sent from the Camel
nded 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 repre
Hi
It depends on the situation but sometimes you could simply let it fail
and rollback to the source.
But what you are looking for is currently not implemented in Camel.
Having its RedeliveryErrorHandler
support non blocking delays.
This is something we will add in the future. I was hoping I got
Yes, but this only increases number of messages that are needed to
"block" the route. What if I have thousands of messages and somewhere
between 1 and 1000 can fail ? I don't want "good" messages to wait for
"bad" messages to exhaust their retries.
If I would set concurrentConsumers=2000 that can
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
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
