Hi, I have a scenario where splitter runs with parallelProcessing().shareUnitOfWork().stopOnException(). It seems that the message headers/properties are not correctly propagated to the errorHandler if simultaneously more Exceptions occur (see the UnitTest attached).
SplitterStopOnExceptionParallelWithExceptionTest.java <http://camel.465427.n5.nabble.com/file/n5741542/SplitterStopOnExceptionParallelWithExceptionTest.java> Actually every Exchange that reaches the ErrorHandler gets the same values for headers/properties. And also what I’m seeing is that only one error-exchange (as expected with shareUnitOfWork()) reports the Error to the Parent-UnitOfWork but the rest of them are not. What exactly is expected behavior in that case? Thanks, best regards, Boris -- View this message in context: http://camel.465427.n5.nabble.com/Headers-not-correctly-propagated-to-the-errorHandler-on-split-tp5741542.html Sent from the Camel - Users mailing list archive at Nabble.com.
