Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: MB-931
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Gary Tully
Reporter: Roddie Kieley
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FUSE Message Broker

Web console shows incorrect number of messages for topic

Created: 29/Jul/11 05:42 PM   Updated: 18/Aug/11 03:25 PM
Component/s: broker
Affects Version/s: 5.4.2-fuse-00-00, 5.4.2-fuse-02-00, 5.5.0-fuse-00-00
Fix Version/s: 5.5.0-fuse-00-53, 5.6.0-fuse-00-00

Environment: OSX 10.6.6, JDK 1.6.0_24, activemq 5.5.0-fuse-00-27, 5.4.2-fuse-02-00, and 5.4.2-fuse-00-00

External Issue URL: https://issues.apache.org/jira/browse/AMQ-3442


 Description  « Hide
Creating a Topic, producing 100 messages to it, starting a consumer that consumes 50 then stops, then when started again and consumes the other 50, leaves the web console showing 100 messages still enqueued when in reality there are none. Original report of issue in DEV-3296, see there for modified example/build.xml file to reproduce the problem.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Gary Tully added a comment - 05/Aug/11 03:15 PM
do you see the same behavior with jconsole?

Gary Tully added a comment - 08/Aug/11 06:30 PM
This issue seems to be just related to the counters.
The enqueueCount for a topic is the number of messages sent to that topic but it is not decremented by consumers, it is increment only. It should be 100. The dequeueCount is always 0 for a topic, because it will quickly exceed the enqueueCount when there are more than one topic subscription.

The inflight count is broken with durable subscriptions when keepDurableSubsActive (default true) is enabled. I will fix this, such that inflight count is decremented when the durable sub goes offline.

The visibility of an offline durable sub can also be improved, the current name "false" is not intuitive. I will fix that also and reuse the subscriptionKey. With keepDurableSubsActive, the subscription is still active so the enqueues/dequeues for that subscription MBean will be correct.


Gary Tully added a comment - 09/Aug/11 05:29 PM
have implemented some improvements on the inflight count and mbean name for an inactive durable sub. I found one case where a durable subscription could not retrieve all messages. It required the broker attribute: keepDurableSubsActive=false (which is not the default). Added a test and a fix in https://issues.apache.org/jira/browse/AMQ-3442

The dequeueCounter is still 0 for a topic and the enqueueCounter reflects messages sent to a topic. Inflight is now updated when a durable deactivates.


Gary Tully added a comment - 18/Aug/11 03:25 PM
merged to 5.5.x