Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: neutral (athena.apache.org: 216.139.250.139 is neither permitted
 nor denied by domain of zackhasit@gmail.com)
Date: Tue, 2 Oct 2012 09:13:01 -0700 (PDT)
From: zackhasit <zackhasit@gmail.com>
To: users@activemq.apache.org
Message-ID: <1349194381328-4657377.post@n4.nabble.com>
In-Reply-To: 
 <CAH+vQmMBC3dsx514gb0PK6RdFG8kiUL29cqPvdUQGUSMm53oLA@mail.gmail.com>
References: <1349187075331-4657353.post@n4.nabble.com>
 <CAH+vQmMBC3dsx514gb0PK6RdFG8kiUL29cqPvdUQGUSMm53oLA@mail.gmail.com>
Subject: Re: Maintenance Mode
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.