activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: ActiveMQ using too much bandwidth
Date Wed, 14 Apr 2010 08:10:12 GMT
Hi John,

maybe you can consider using network of brokers over the WAN and then
connect your consumers locally to the second broker. That will give you
better bandwidth and more fail tolerant solution.

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Wed, Apr 14, 2010 at 3:56 AM, john robens <jrobens@interlated.com.au>wrote:

> Hi
>
> We are trying to use activemq/camel to keep a web-site external to the
> organisation in sync. We send a delta update every 10 minutes.  Because it
> is hosted outside the organisation there are bandwidth limits.
>
> We are using ActiveMQ with Apache Camel and there are 2xroutes. The
> 2xroutes/queues are the the route that runs every 10 minutes and one that
> runs daily. This configuration results in approximately 50kb/s of traffic -
> openwire negotiations and temporary topic/queue information.
>
> We are interested in tuning this - can activeMQ be set to only perform
> advisory updates slowly? Once a minute would be fine as this is a low
> latency application. We were planning on rolling this type of technology out
> to 1000 clients to keep them up-to-date - at this scale this traffic would
> be quite expensive.
>
> ActiveMQ spring config is simply:
>
> <broker:broker useJmx="false" persistent="false" brokerName="tcp">
>         <broker:destinationPolicy>
>             <broker:policyMap>
>                 <broker:policyEntries>
>           <!--          <broker:policyEntry topic=">"
> advisoryForConsumed="true"/>  -->
>                 </broker:policyEntries>
>             </broker:policyMap>
>         </broker:destinationPolicy>
>
>         <broker:transportConnectors>
>             <broker:transportConnector name="tcp" uri="${activemq.uri}"/>
>         </broker:transportConnectors>
>     </broker:broker>
>
>
> Attached is a pcap file with transactions and data dump.
>
>
> Maven project, simply deployed as a spring jar with:
> Activemq :5.3.0
> Camel: 2.2.0
>
> Thanks
> John
>
> --
> http://interlated.com.au
> 0434 996 607
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message