camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thibaut Robert (JIRA)" <>
Subject [jira] [Commented] (CAMEL-9791) DeadLetterChannel not triggered on RejectedExecutionException
Date Sun, 10 Apr 2016 18:52:25 GMT


Thibaut Robert commented on CAMEL-9791:

[] Thanks for the fix ! It works fine with {{ThreadPoolRejectedPolicy.Abort}}.

However I think it breaks the logic of {{ThreadPoolRejectedPolicy.Discard}} or {{ThreadPoolRejectedPolicy.DiscardOldest}}:
The exchange will continue to be executed by the calling thread instead of being discarded.

Also, would it be possible to add a {{ThreadPoolRejectedPolicy.AbortOldest}} logic too ? 

> DeadLetterChannel not triggered on RejectedExecutionException
> -------------------------------------------------------------
>                 Key: CAMEL-9791
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.17.0
>            Reporter: Thibaut Robert
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.18.0
>         Attachments:
> 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

View raw message