[
https://issues.apache.org/jira/browse/CAMEL-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9791.
Resolution: Fixed
Will now use rejection policy if configured and only fallback to caller run if
none was set.
And abort, discard et all are all rejected, as the exchange needs to rejected
so it can no longer be inflight and do its uow done work.
No need for discard abort.
> 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
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.18.0
>
> 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)
