[
https://issues.apache.org/jira/browse/CAMEL-10660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-10660.
---------------------------------
Resolution: Won't Fix
Assignee: Claus Ibsen
This is by design currently.
> InterruptedException not handled by RedeliveryErrorHandler
> ----------------------------------------------------------
>
> Key: CAMEL-10660
> URL: https://issues.apache.org/jira/browse/CAMEL-10660
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.16.3
> Reporter: Ralf Steppacher
> Assignee: Claus Ibsen
>
> It appears that if the exception on an {{Exchange}} is of type
> {{InterruptedException}} or if any exception in the cause-chain is of that
> type, then that exception is completely ignored by the
> {{RedeliveryErrorHandler}}. Possibly because it is assumed that any
> {{InterruptedException}} would have been raised is due to a Camel context
> shutdown?
> See {{RedeliveryErrorHandler::isDone(Exchange exchange}}.
> It would be great if {{InterruptedException}} not associated with the Camel
> context life-cycle could be treated like any other exception (logging,
> re-delivery, etc.). As it is now they are neither logged nor handled, which
> might obscure problems in application code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
