FAULT is not propagated over JMS binding in SwitchYard

Solution Verified - Updated -


  • We have two SwitchYard applications (two switchyard.xml). Each of them has only one Camel XML route as implementation. They are connected via JMS binding, i.e.:

    [ ServiceA - RouteA - ReferenceA ] - JMS - [ ServiceB - RouteB - ReferenceB ]
  • ReferenceB encounters a SOAPFault. This fault is properly progagated back to ServiceA (the Exchange state is always FAULT).

  • However, when the message enters ReferenceA after being transferred over JMS, the fault switch is lost. The Exchange is in state OK, even though the message contains the SOAPFault.


  • Red Hat JBoss Fuse Service Works (FSW)
    • 6.0
  • Red Hat JBoss Fuse (Fuse)
    • 6.2
  • SwitchYard

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