Hi, you can consider using smaller prefetch size (1 or so) which will make local broker send one message at the time. This could slow down the NC and thus help with your bandwidth.
Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Jun 21, 2011 at 12:20 PM, nw <nick...@gmail.com> wrote: > Hi, > > I have a store and forward network of brokers (A), with one broker at a > different geographical location (B) which consumers (C) are processing > messages from. Our problem is bandwidth restrictions from A to B. > > My question is, is it possible to rate limit messages that are forwarded > from A to B? I looked at BrokerFilter, but that is designed to > accept/reject > connections and sadly not individual messages. > > I was thinking of something like having access to the underlying > InputStream, then reading a number of bytes, sleeping for a few millis, > etc. > > I don't think ActiveMQ Streams are what we'd like; the splitting of the > data > into seperate JMS messages will confuse monitoring systems, and the lack of > ability to replay messages if the consumer fails isn't good. > > Using message blobs would require a shared resource between the consumers C > and the producers that feed A, where none exists in my system. > > Thanks, > > Nick > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Rate-limiting-message-uploads-to-a-broker-tp3613653p3613653.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
