d 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 the Camel - Users mail
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
--
View this message in context:
http://old.nabble.com/Message-blocks-route-until-all-redelivery-attempts
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
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
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
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
