4 Replies Latest reply on Mar 18, 2013 2:48 AM by njiang

Camel doesn't recognize faults as exceptions

alexander.durnev Mar 1, 2013 3:39 AM

I've encountered a very strange problem with Fuse ESB 7.1.0: when a cxf endpoint produces a fault, then this fault doesn't look like an exception, so I can't process it using doCatch construction.

The cxf endpoint is defined as follows:

And here is a short code snippet where I expect an exception:

I've tried to add handleFault="true" attribute to both a camel context and a route, but without success.

A bundle with a similar parameters and routes has worked as expected on Fuse ESB/ServiceMix 4.4.1, so it looks like a regression or maybe something has changed in camel in the new release?

Another interesting moment is that when a web server is not available, then camel produces org.apache.cxf.interceptor.Fault, so it can't be handled as an exception!

Edited by: alexander.durnev on Mar 1, 2013 8:39 AM

1. Re: Camel doesn't recognize faults as exceptions

alexander.durnev Mar 4, 2013 6:46 AM (in response to alexander.durnev)

I use a cxf jaxws client bean as a workaround currently.
Actions
2. Re: Camel doesn't recognize faults as exceptions

njiang Mar 5, 2013 7:50 AM (in response to alexander.durnev)

It is strange, I just wrote an unit test but cannot reproduce the error.
Can you paste the full camel route ?

The change of camel-cxf recently is to honor the Message Exchange Pattern. But I don't think it could cause the trouble that you meet.
Actions
3. Re: Camel doesn't recognize faults as exceptions

alexander.durnev Mar 11, 2013 4:09 AM (in response to njiang)
My camel context looks as following (I've simplified it):

-

-

I've performed the following steps:
I've changed targeted web service parameters, so it references on the non-existent server;
I've performed a request to the bundle via http;
I see the trace back with "Connection refused" message in the log file, but with WARN level (!!!), so it has logged outside of my bundle;
I don't see a log entry with ERROR level that I've expected;
I see that the route wasn't stopped and a secondRoute was executed, so I'm absolutely sure that the doCatch instruction wasn't executed.
Actions
4. Re: Camel doesn't recognize faults as exceptions

njiang Mar 18, 2013 2:48 AM (in response to alexander.durnev)

Hi,

I wrote some simple test to reproduce the error, but I cannot reproduce it.
From the route and you description, I cannot tell anything wrong.
Can you just try to send a simple test case for us to reproduce the error?

Regards,

Willem
Actions

Go to original post