Streaming is a good idea to use if you do not need to know the total size in advance. As with streaming the splitting is done in an iterated fashion, where as non streaming the iteration is done on a list (eg to know the total size)
On Thu, Aug 1, 2013 at 5:23 PM, jasonor <a444...@fmr.com> wrote: > Hi Claus, thanks for the response. > > The payload size here is quite small here ~30k so i didn't streaming was the > issue. Is there a ball park size where streaming should be enabled? > > I'm wondering is there something that is keeping these messages active/not > eligible for garbage collection. The size of MulticastProcessor is in the > thousands that that's what's filling up the heap. I've seen an 'end' marker > on some examples, am i missing something as simple as that? > > Thanks, > Jason > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Multicast-Memory-HeapSize-issue-tp5736641p5736644.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 in Action: http://www.manning.com/ibsen
