ion [1].
>
>
> Justin
>
> [1] http://activemq.apache.org/artemis/docs/1.2.0/flow-control.html
>
> - Original Message -
> From: "Bilgin Ibryam"
> To: users@activemq.apache.org
> Sent: Tuesday, February 2, 2016 5:54:28 AM
> Subject: Re: Consumer th
t;Bilgin Ibryam"
To: users@activemq.apache.org
Sent: Tuesday, February 2, 2016 5:54:28 AM
Subject: Re: Consumer throttling
Thanks all for your inputs. It seems there is no solution for my
question in ActiveMQ yet.
@Christopher: I'm aware of scheduling feature, but that is more of a
Dela
Thanks all for your inputs. It seems there is no solution for my
question in ActiveMQ yet.
@Christopher: I'm aware of scheduling feature, but that is more of a
Delayer rather than Throttler. It can delay messages, but cannot
ensure throttled consumption. If I get a burst of messages delay them,
at
You could achieve your goal by having two queues, A and B. Have producers
publish to A and consumers consume from B, and use an embedded Camel route
to move messages from A to B at the desired rate.
But Raul's right: if you're going to do this, make sure there's some kind
of safety feature to pre
Just one remark. This could be dangerous as it could lead to an
ever-growing backlog of messages in AMQ. I suppose you have already
considered it, and either the producers are slower than the consumers, or
you have multiple competing consumers, or there is a period in the day
where the producers st
The only thing built in would be the scheduling feature. Take a look at
http://activemq.apache.org/delay-and-schedule-message-delivery.html
This allows you to delay a message or schedule so this may work for you.
Otherwise I think you will have to continue using client logic if you want
to thrott
