Re: Exception in second inOut jms endpoint returns null body to aggregation strategy

I've trimmed my code to the bear minimum. If I throw the exception in my first call to the child route, then I get the body returned to my aggregation strategy, but when I throw an exception on my second call the body is null when I get to the aggregation strategy. Why would this be? -

Re: Null Body

After further analysis I've decided it has nothing to do with the marshalling and unmarhalling. In my main route inside the split I make to inout calls, if an exception is thrown in the second inout call, then I loose the body. I can swap the two and it always happens in the second one. -- View

Re: Null Body

Thanks for the quick response. I tried setting streamcache to true on the route, but no luck. I believe it has something to do with the unmarshalling to jaxb, if I throw an exception before the unmarshal, then the body returned to the parent route is not null. If add a processor to my onException,

Null Body

I have two routes, the parent route uses jms with the inout EIP to call the below route, and uses the transferException parameter so that exceptions get returned to the parent route. The problem is that in my child route I unmarshal using jaxb before calling a bean, when an exceptions occurs in tha