Yes mock keeps a copy of the exchange in memory. Though you can use retainFirst/retainLast option to only keep X number of copies. Read more about the mock at its website.
On Thu, Jan 23, 2014 at 3:36 AM, contactreji <[email protected]> wrote: > Hi All > > I was using mock component as a sink element in one of the stubs i had > created representing a destination system. > > Once pushed to mock:end, it is not used by any assertions statements / > logic. > > *I wanted to know if the exchanges pushed to mock:end component will stay in > memory or is the exchange destroyed by Garbage collector. > * > I am pushing about 50 xml data to mock:end every second. Would that over a > period of time, fill up the jvm? > > Regards > Reji Mathews > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-mock-end-tp5746370.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
