You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by emc2family <em...@gmail.com> on 2008/12/13 11:29:12 UTC
relationship between per destination memory limit vs broker memory
limit
Hi,
it sounds like per destination memory limit is a sub-allocation of the
broker's system usage memory limit. in other words if broker mem limit is
50 mb, then per destination mem limit is part of that instead of in addition
to that. if anybody can confirm this please i'd appreciate it. thanks a
bunch.
--
View this message in context: http://www.nabble.com/relationship-between-per-destination-memory-limit-vs-broker-memory-limit-tp20988921p20988921.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: relationship between per destination memory limit vs broker memory limit
Posted by Rob Davies <ra...@gmail.com>.
On 13 Dec 2008, at 10:29, emc2family wrote:
>
> Hi,
>
> it sounds like per destination memory limit is a sub-allocation of the
> broker's system usage memory limit. in other words if broker mem
> limit is
> 50 mb, then per destination mem limit is part of that instead of in
> addition
> to that. if anybody can confirm this please i'd appreciate it.
> thanks a
> bunch.
> --
> View this message in context: http://www.nabble.com/relationship-between-per-destination-memory-limit-vs-broker-memory-limit-tp20988921p20988921.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Yes - that's correct! - the system usage always overrides the
destination memory too - so if you have 10mb of space left in a
destination - but none left in the broker's overall memory (used up by
other destinations) - then you're producers will still block ...
cheers,
Rob
Rob Davies
http://fusesource.com
http://rajdavies.blogspot.com/