Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-9791

DeadLetterChannel not triggered on RejectedExecutionException

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 2.17.0
    • 2.17.1, 2.18.0
    • camel-core
    • None
    • Advanced

    Description

      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.

      Attachments

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            davsclaus Claus Ibsen
            trobert Thibaut Robert
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment