You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Thibaut Robert (JIRA)" <ji...@apache.org> on 2016/04/03 23:05:25 UTC
[jira] [Comment Edited] (CAMEL-9791) DeadLetterChannel not
triggered on RejectedExecutionException
[ https://issues.apache.org/jira/browse/CAMEL-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223513#comment-15223513 ]
Thibaut Robert edited comment on CAMEL-9791 at 4/3/16 9:04 PM:
---------------------------------------------------------------
Here is a unit test
was (Author: trobert):
test case
> DeadLetterChannel not triggered on RejectedExecutionException
> -------------------------------------------------------------
>
> Key: CAMEL-9791
> URL: https://issues.apache.org/jira/browse/CAMEL-9791
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.17.0
> Reporter: Thibaut Robert
> Priority: Minor
> Attachments: ThreadsRejectedExecutionWithDeadLetterTest.java
>
>
> I use a thread processor to implement multi-threading
> I wish that the deadletter endpoint of the route to be called when the pool reject the execution of the task (to save the message on disk)
> However, whatever the rejectedPolicy I choose, the rejected exchange is just dropped because the exchange is marked with routeStop and redeliveryExhausted.
> I think it's correct to not redeliver (we are lacking resources, replaying won't help), but there should at least be a way to handle the failed message somehow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)