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 stop producing to give the consumers time to consume the existing backlog or something.
If you implement this, I would reduce the prefect buffer to 1 if you have multiple competing consumers to achieve decent distribution and avoid starvation. Raúl. On 30 Jan 2016 18:15, "Bilgin Ibryam" <[email protected]> wrote: > Hi all, > > Apologoes if this is a stupid question. But I wonder is there a way to > do throttling on the consumer side. Let me clarify what I mean. > > PFC can do throttling for the producer, but I need a similar behaviour > on the consumer. For example I want to configure a message consure or > message queue so that messages are consumed/released one per second. > Usually the messages are consumed as fast as the cosnumers can take. > Then I can do some throttling in consumer Camel route, but that > throutling in Camel cannot be clustered accross instances. If the > throttling can be configured ot queue level, then I don't have to do > consumer throttling. > > Thanks, > > -- > Bilgin Ibryam > Camel Committer at ASF & Integration Architect at Red Hat > Blog: http://ofbizian.com | Twitter: @bibryam > > Camel Design Patterns https://leanpub.com/camel-design-patterns > Instant Apache Camel Message Routing http://www.amazon.com/dp/1783283475 >
