activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Usage memory Limit hit with Network of Brokers.
Date Tue, 03 May 2011 09:20:37 GMT
you need to use a pending message limit strategy or file pending
message cursor. In your setup, when one of the networked brokers goes
down it becomes (looks like) a very slow consumer.

Check out the options: http://activemq.apache.org/slow-consumer-handling.html

On 28 April 2011 14:29, manua <agarwal.manu@gmail.com> wrote:
> HI,
>
> I setup a network of brokers between 3 brokers as,
>
> <networkConnectors>
>        <networkConnector name="amq3"
> uri="static:(tcp://amq1.com:61616,tcp://am2.com:61616)" duplex="true"/>
> </networkConnectors>
>
> (similarly made settings on other two brokers as well)
>
> The messages being published on one topic were distributed to all three
> brokers.
> When on of the broker went down, the memory message limit was hit on other
> brokers and the system crashed.
>
> The same setup was working fine without network of brokers (no memory limit
> was being hit with single broker).
>
> Does it mean that in network of broker setup, one broker acted as durable
> consumer on topics for other brokers.
>
> How can I avoid the memory limit from being hit, with network of brokers or
> what is the best way to have high availability activemq setup.
>
> Thanks,
> Manu
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Usage-memory-Limit-hit-with-Network-of-Brokers-tp3480996p3480996.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
http://blog.garytully.com
http://fusesource.com

Mime
View raw message