SwitchYard Exception handling in the event a binding is broken

Solution Verified - Updated -


SwitchYard can suffer exceptions that are very difficult to manage when the problem area involves a broken binding. One example:

  • SwitchYard uses a Camel component (with try/catch) that attempts to call out to a SwitchYard Reference. The Reference uses a Camel 'VM' connection.
  • The called vm endpoint (defined in a Camel route) isn't available. Note that no error will be thrown at runtime, this is not detectable at deployment time.
  • When the unavailable endpoint is invoked, neither SwitchYard nor Camel can be coerced to process any pipeline actions. The exchange is populated with an org.switchyard.HandlerException and no try/catch steps, further actions, etc are available.


Fuse Service Works 6.0
Fuse 6.x

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