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

Exception thrown during JAXB marshalling will cause SedaConsumer to break

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.8.0
    • 2.8.1, 2.9.0
    • camel-jaxb
    • None
    • Unknown

    Description

      Error handler tries to add message body to error log. If it tries to use JAXB type converter and marshalling throws exception, the exception is thrown all the way back to SedaConsumer. SedaConsumer will then retry to create error message in the same way until the point where exception is not handled any more and SedaConsumer loop breaks off.

      One single bad message can stop Seda route.

      Attachments

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

          People

            davsclaus Claus Ibsen
            dragisak Dragisa Krsmanovic
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment