FAULT is not propagated over JMS binding in SwitchYard - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Issue

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.

Environment

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

New to Red Hat?

Learn more about Red Hat subscriptions

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

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)