If you body is big that you are splitting, then you can consider using
streaming mode on the splitterl
On Thu, Aug 1, 2013 at 4:04 PM, jasonor <a444...@fmr.com> wrote:
> Hi, i have quite a simple route which uses a <split> and a <multicast>
> along the lines of ....
> <split>
> <simple>${body}</simple>
> <bean ref="aBean" method="doA" />
> <multicast>
> <to uri="seda:createX" id="sedaCreateX" />
> <to uri="seda:createY" id="sedaCreateZ" />
> </multicast>
> </split>
>
> I'm seeing HeapSize filling up,
> Diving into the heapsize more i see a large object array of type of type
> org.apache.camel.processor.MulticastProcessor$DafaultProcessorExchangePair
> which looks to be consistent with the size and volumes of messages going
> through the route.
>
> Has anyone encountered the likes of this before? I'm wondering is there an
> 'end' missing?
>
> Appreciate the help,
> Jason
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Multicast-Memory-HeapSize-issue-tp5736641.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
