You can change the memory limits via JMX without a restart. JMX allows you
to not only monitor, but interact with the MBeans that are exposed and have
operations and attributes. From within a JMX console, navigate to the
destination in question, find the "MemoryLimit" attribute which denotes
memory in bytes, and change it. Only the producers to that one destination
would be blocked, not producers to all destinations. If a producer is
producing to a different destination, it will not be blocked.

On Tue, Oct 2, 2012 at 9:13 AM, zackhasit <zackhasit@gmail.com> wrote:

> Does memory limit change via JMX require restart ? (I am not familiar with
> JMX but does that allow changes to broker properties also ? I thought it
> was
> just a monitoring interface ... )
>
> Can I set memory limit of a queue to zero such that producers cannot write
> at all while consumers consume all pending messages ? Would that could make
> the queued messages drop down to zero ?
>
> You mentioned about producers blocking until more space is available in a
> queue. However can this be non blocking so that producer can send messages
> to other queues meanwhile? (Note that I am trying to stop consumers for
> maintenance to a particular queue only and broker might have more queues
> that would keep functioning)
>
> This is for non persistent queues.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Maintenance-Mode-tp4657353p4657377.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
*Christian Posta*
http://www.christianposta.com/blog