Bug 1202701 – (6.0.x) Unexpected behavior in fault handling with doTry/doCatch in Camel service

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1202701 - (6.0.x) Unexpected behavior in fault handling with doTry/doCatch in Camel service

Summary:	(6.0.x) Unexpected behavior in fault handling with doTry/doCatch in Camel ser...

Status:	VERIFIED

Aliases:	None

Product:	JBoss Fuse Service Works 6
Classification:	JBoss
Component:	Camel (Show other bugs)
Sub Component:
Version:	6.0.0 GA
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	kconner
QA Contact:	Matej Melko
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1202699
Blocks:	1183067
	Show dependency tree / graph

Reported:	2015-03-17 05:12 EDT by Tadayoshi Sato
Modified:	2015-11-02 03:12 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:	1202699
Environment:
Last Closed:
Type:	Support Patch
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Apache JIRA	CAMEL-8476	None	None	None	Never

Groups: None (edit)

Description Tadayoshi Sato 2015-03-17 05:12:39 EDT

+++ 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.

Note You need to log in before you can comment on or make changes to this bug.