camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-9791) DeadLetterChannel not triggered on RejectedExecutionException
Date Mon, 04 Apr 2016 14:20:25 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated CAMEL-9791:
-------------------------------
    Fix Version/s: 2.18.0

> 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)

Mime
View raw message