+++ This bug was initially created as a clone of Bug #1202699 +++ Platform BZ for https://issues.apache.org/jira/browse/CAMEL-8476 We have two Camel routes with doTry/doCatch for the entire route and a target SOAP endpoint that can throw SOAP faults. When the second Camel route receives a SOAP fault, the fault gets through the doTry/doCatch for both routes as they don't set handleFault=true flag. In the first route, however, the SOAP fault is just processed as state OK despite our expectation that it should be handled as FAULT. Furthermore, if we add any arbitrary processor (e.g. <log message="xxx"/>) after the end of doTry in the second route, then surprisingly we get an expected behaviour. That is, the fault is handled as state FAULT in the first route as well. See CAMEL-8476 for the explanation on why this behaviour happens. Attached please find the reproducer project that is based on the 'camel-soap-proxy' quickstart. Run 'mvn test' to observe what is outlined above.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.