camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Memory leak in stub component
Date Tue, 05 Jan 2016 18:49:58 GMT
Yes its by design. See the retain options on the mock endpoint to
limit how many.

On Tue, Jan 5, 2016 at 7:40 PM, dancerjohn <winddancerjohn@gmail.com> wrote:
> We have a system that published to several JMS topics. This system processes
> several million exchanges a day. In our integration environment we are still
> processing the same number of exchanges but we don't want to publish to JMS
> (or might want to publish to some topics but not others). We way I thought
> would be appropriate to do this was to configure the URI for the route to
> "stub:blah1", "stub:blah2", etc. Replacing the JMS URI with a stub URI.
>
> When doing this there appears to be a memory leak. It appears that each
> exchange is being held in the Queue in the underlying Seda component. My
> expectation was that when the route hit the stub, it would just basically
> skip that step and move forward.
>
> Is this by design? Is there something else I should use for this? If this is
> by design because the stub component should only be used in short-lived
> environments (like unit testing), I think the documentation page should be
> made more explicit.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Memory-leak-in-stub-component-tp5775851.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Mime
View raw message