Did you consider using blob messages ( http://activemq.apache.org/blob-messages.html). This would have your JMS messages be small and the actual payload transferrer using some other server (FTP for example).
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 Wed, Jun 22, 2011 at 10:43 PM, nw <nick...@gmail.com> wrote: > Hi, > > Thanks for your reply. Your solution would be good. Unfortunately there is > another constraint that I failed to mention; the messages are rather large, > with the capacity to go up to at least 5 Megs. > > If we add this to the example with your suggestion applied, even a single > message would saturate the upstream from A to B until it was uploaded. > > Thanks, > > Nick > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Rate-limiting-message-uploads-to-a-broker-tp3613653p3618192.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
