Ah i forgot to mention that the above route is preceeded by another route,
with its own errorHandler:
[code]
dlcb = new
DeadLetterChannelBuilder(Constants.MAIN_INBONUND_QUEUE+"/deadLetter");
dlcb.setFailureProcessor(new MyLoggingProcessor("Message
Delivery
Failure"));
...
@Override
public void configure() throws Exception {
from(Constants.MAIN_INBONUND_QUEUE)
.errorHandler(dlcb.maximumRedeliveries(redeliveriesCount).redeliveryDelay(redeliveryDelay).onRedelivery(new
MyLoggingProcessor("Message redelivery in progress.")))
.threads(routeExecutionThreadCountCount)
.multicast().parallelProcessing().to(Constants.ANOTHER_QUEUE,
Constants.INBOUND_QUEUE)
;
[code]
and that even if the failure occurs on the second route (the one described
in the previous message) I notice this error handler is also involved, and I
can't figure out why really...
The error I situation I am testing is the "DuplicatedMessageException" one.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-9-1-DeadLetterChannel-infinite-loop-tp5714961p5714963.html
Sent from the Camel - Users mailing list archive at Nabble.com.
