[CAMEL-5164] Camel error handler stop routing on original route when an exception occur in the splitter using jaxb marshalled objects

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.1
• Fix Version/s: 2.9.3, 2.10.0
• Component/s: camel-core, camel-jaxb
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Luca Foppiano
• Created: 11/Apr/12 21:12
• Updated: 17/Jul/12 22:12
• Resolved: 18/Apr/12 16:51

Description

I've been digging into this problem for some time now and I haven't find why this is happening. I'm using camel 2.9.1.
The whole problems is quite complicated to explain, I've created a test that reproduce the error that might be more useful.

I have a route that get some XML and transform it with a processor in an object generated from XSD with JAXB. After that the object (transported as XML) is then split based a certain logic. The route uses the deadLetterCHannel error handler to a 'reject' endpoint.

Now, sometimes when I get some invalid character in the input file (0x10 eg.) (in my processor I don't polish them), the splitter will crash but, instead of detouring only the messages that contains errors to the deadLetterChanne, it will detour every message coming after the error occurs.

I know that I can fix the problem in the processor by removing the invalid characters, but in my opinion, camel should be more robust and doesn't block the entire processing for a "non fatal" error. Or I should use a different way for doing what I'm doing...

Please have a look at the code and let me know, I think is a bug but I'm waiting for your opinion.

Thanks in advance

Issue Links

• depends upon: CAMEL-5172 TypeConverter - Tighten up API to rethrow failed exception during type conversion, and introduce new API for try to convert