Hi, You are using a very old version of Camel which we don't plan to support. I just checked the source code in the trunk, I think current camel splitter has a better solution of stopOnException. Did you try to use the latest released Camel 2.10.4 to see if the error is still there?
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Friday, March 15, 2013 at 2:21 AM, khar wrote: > Hello All! > > I'm using Camel 2.2 and I'm trying to split incoming message, then process > them parallelly (with my own thread pool), then aggregate them with my > custom AggregationStrategy. Everything works fine except of error handling - > I don't need any of those splitted messages if any of them throws an > exception, and I don't wan't to process others in case of such exception. To > do so I'm using stopOnException(). But from what I see, when I use it, and > there is an exception on my route none of the failed messages goes to the > AggregationStrategy. > > So my quiestion is: is there any way to make stopOnException() and custom > AggregationStrategy work together, and if not then how can I stop other > threads from processing their requests in case of exception without using > stopOnException (for example how to handle it in my AggregationStrategy?)? > > Thank you for all your help! > > Mikolaj Kromka > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-2-2-Exception-handling-problem-in-case-of-parallel-splitter-with-custom-AggregationStrategy-tp5729205.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
