activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: Negative Queue Size in 5.3.2
Date Thu, 21 Jun 2012 10:19:43 GMT
that looks like a sync issue between the jmx op and the destination
w.r.t counters.
Possibly messages that are dispatched and inflight to the consumer are
getting removed so they are acked twice.
inflight messages should really be invisible to a remove message call
via jmx but I guess that is debatable.

Could you try your scenario with the current 5.6 release to see if it
is still reproducible.
What is the intent here?
Unlike competing consumers, the jmx op bypasses dispatch, so if you do
the jmx op when there are no consumers I would expect
different behavior.

If you want to limit the queue size, message expiry is the preferred way to go.

On 20 June 2012 20:00, patsfan <> wrote:
> Hi All,
> We are running into a case where our queue size is < 0 via both the
> webconsole and via jmx in 5.3.2.  Here is our scenario:
> VM1: looping 5000 times, each time pushing a message into a queue
> VM2: listening on the queue (1 listener) and processing the messages
> VM2: responds to a REST call by purging messages from the queue by a
> particular property (QueueViewMBean.removeMatchingMessages(...)).
> After calling QueueViewMBean.removeMatchingMessages(...) (deletes > 1K
> messages from the queue) the queue size goes negative.  Saw a few posts that
> are related, but they go back a few years with no clear resolution.
> Has anyone seen this?  Please let me know if you need additional
> information, would gladly supply.
> Thanks in advance,
> Al
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at


View raw message