[
https://issues.apache.org/jira/browse/CAMEL-20744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848221#comment-17848221
]
Bert Speckels commented on CAMEL-20744:
---------------------------------------
I can confirm that allowRedeliveryWhileStopping=false is a solution. However, I
discovered two problems:
1. If the route aborts the redelivery, the processing is interpreted as
successful. I'm wondering if this is the expected behavior. This prevents the
sending system (RabbitMQ) from redelivering the message once the route becomes
available again.
2. 'allowRedeliveryWhileStopping=false' only works if I stop the exact route
that does the redelivery. But I have route A ("from:spring-rabbitmq"), which
forwards directly to route B ("direct:send"): A--direct-->B. When I stop route
A (so that the rabbitmq listener is terminated) then the redelivery continues
in route B ("sending"). That was also different with using “camel rabbitmq”.
> camel-core - Error handler redelivery to support option to break out if
> stopping
> --------------------------------------------------------------------------------
>
> Key: CAMEL-20744
> URL: https://issues.apache.org/jira/browse/CAMEL-20744
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.x
>
>
> We can maybe add an option to error handler / onException
> retryWhileStopping = true|false
> This means that Camel will stop doing retries/redeliveries when CamelContext
> is stopping / or that the current route is being stopped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
