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

StreamResequencer logs unhandled Exceptions at DEBUG level

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.7.1
    • 2.8.1, 2.9.0
    • camel-core
    • None

    • Linux JDK 1.6.0_20

    • Unknown

    Description

      If an unhandled Exception is caught by StreamResequencer.run(), it effectively logs the Exception at DEBUG level. A thrown Exception can indicate that a delivered message was not fully processed (as is the case in my route), so this means a message is dropped with a notification in the log only at DEBUG level. This is highly undesirable in a critical route.

      It should at least be logged at WARN level, and preferably should be handled using the configured ErrorHandler for the route.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. CAMEL-4264 The routeContext stack of DefaultUnitOfWork should be thread safe

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              davsclaus Claus Ibsen
              dgtombs David Tombs
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: