[
https://issues.apache.org/activemq/browse/AMQ-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Loc Truong updated AMQ-2186:
----------------------------
Component/s: (was: Broker)
Message Store
Fix Version/s: (was: 5.2.0)
Description:
1. The Queues list displays a number, "Number Of Pending Messages" for like
1000.
2. When clicking on that queue, the number of message (total of all rows) is
smaller than 1000.
Actually the #2 always displays a very small number of messages which is not
more than 100 although the number on the list keep increasing to like forever.
The problem doesn't happen when ActiveMQ starts but after one to a few hours
instead. At the moment the only way to resolve this at our end is to restart
the AMQ.
was:
When you "purge" queue from web admin console, it zeroes queue message
counter. But if you have an active consumer at that time which
pre-fetched messages than your consumer will keep sending ack as it
process messages from its buffer. ActiveMQ will keep decrement counter
upon receiving each ack. So when consumer is done queue will show
MINUS<consumer buffer size>.
Environment: CentOS 5.2 64bit (was: Found on Windows but reproduced
under Linux)
Regression: (was: [Regression])
> Number of messages when browsing queue is different to "Number Of Pending
> Messages" in queue list
> -------------------------------------------------------------------------------------------------
>
> Key: AMQ-2186
> URL: https://issues.apache.org/activemq/browse/AMQ-2186
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.2.0
> Environment: CentOS 5.2 64bit
> Reporter: Loc Truong
> Assignee: Rob Davies
> Priority: Critical
>
> 1. The Queues list displays a number, "Number Of Pending Messages" for like
> 1000.
> 2. When clicking on that queue, the number of message (total of all rows) is
> smaller than 1000.
> Actually the #2 always displays a very small number of messages which is not
> more than 100 although the number on the list keep increasing to like forever.
> The problem doesn't happen when ActiveMQ starts but after one to a few hours
> instead. At the moment the only way to resolve this at our end is to restart
> the AMQ.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
