You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Ralf Steppacher (JIRA)" <ji...@apache.org> on 2016/12/28 15:58:58 UTC
[jira] [Created] (CAMEL-10660) InterruptedException not handled by
RedeliveryErrorHandler
Ralf Steppacher created CAMEL-10660:
---------------------------------------
Summary: InterruptedException not handled by RedeliveryErrorHandler
Key: CAMEL-10660
URL: https://issues.apache.org/jira/browse/CAMEL-10660
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.16.3
Reporter: Ralf Steppacher
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)