Yes the throttle is in-memory queue based, so you could end up eating up memory.
There is a route policy that can also throttle by suspending/resuming
the actual route, which then would mean that if the route is suspended
then no new incoming messages comes in.
On Wed, Aug 14, 2013 at 11:23 AM, kiranreddykasa <kirankuma...@fss.co.in> wrote:
> Hi
>
> consider this simple route
>
> from("netty:tcp://0.0.0.0:7004?textline=true").throttle(100).to("netty:tcp://0.0.0.0:7005?textline=true");
>
> According to this only 100 requests per second will be sent to second
> endpoint.
>
> Assume that first endpoint is receiving some thousand messages per second,
> how camel is able to throttle these messages without saving anywhere ?
> There won't be any out of memory issues ??
> Can anyone please explain ?
>
>
>
> -----
> Regards
>
> kiran Reddy
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-threshold-tp5737136p5737239.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
