this message in context:
http://camel.465427.n5.nabble.com/Splitter-Problem-with-stopOnException-when-using-threadPoolExecutor-tp5737562.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.n5.nabble.com/Splitter-Problem-with-stopOnException-when-using-threadPoolExecutor-tp5737562.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel
.
--
View this message in context:
http://camel.465427.n5.nabble.com/Splitter-Problem-with-stopOnException-when-using-threadPoolExecutor-tp5737562p5737570.html
Sent from the Camel - Users mailing list archive at Nabble.com.
the aggregationStrategy to propagate back the
exception. As in this case I have the same behaviour and only for checking:
threadPool shouldn´t interfere in this case, right?
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/Splitter-Problem-with-stopOnException-when