On Wed, Jan 5, 2011 at 12:11 PM, rsteppac <[email protected]> wrote: > > Hello Claus, > > thanks for your speedy answer! > > > Claus Ibsen-2 wrote: >> >>> Setting ‘streaming = "true"’ breaks error handling: [..] >> >> Can you try 2.6-SNAPSHOT as we have fixed some issues in relation to >> error handling and splitter/multicast. >> > > The problem is still present in the 2.6 snapshot. I have raised CAMEL-3498. >
As said on this JIRA please attach a sample test case and pin point what you think is wrong. > > Claus Ibsen-2 wrote: >> >>> Setting ‘streaming="true" parallelProcessing="true"’ consumes large >>> amounts >>> of heap space for big original messages. [..] >> >> Hmm I was hoping that a Future instance would be a light weight object >> in Java, but had my hopes to high :) >> > > I have raised CAMEL-3497. > > > Claus Ibsen-2 wrote: >> >> Back in the early days we did have some code using a >> CompletionService. We most likely need to introduce this back and have >> logic to aggregate the result as they fly in. Please create a ticket >> for this issue. >> > > Hm.. > MulticastProcessor::doProcessParallel(Exchange,AtomicExchange,Iterable,boolean,AsyncCallback) > does use a CompletionService. As I understand it the problem is not the > Future objects themselves, but the context of the corresponding callable > (ProcessorExchangePair in line 228 and the Exchange in line 229). The > context cannot go away until the Callable goes away. I think this is where > the memory goes. But it is surely a good idea to look at it with a good > memory profiler. ;-) > > > Ralf > -- > View this message in context: > http://camel.465427.n5.nabble.com/2-Bugs-in-Splitter-Camel-2-5-0-tp3326727p3328590.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
