In Fuse 6.2.x, a Camel onCompletion handler no longer has access to the exception that caused the route to stop

Solution Verified - Updated -

Issue

In Fuse 6.1 (Camel 2.12) a handler invoked using Camel's onCompletion() mechanism could determine which exception caused the route to complete, if it was stopped by an exception. This was done by calling Exchange.getException() in the handler.

As of Fuse 6.2 (Camel 2.15) this mechanism is no longer supported -- Exchange.getException() always returns null, unless an exception has been thrown in the handler itself.

Environment

  • Red Hat JBoss Fuse
    • 6.2.0
    • 6.2.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.