You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Joe Fernandez (JIRA)" <ji...@apache.org> on 2008/09/22 19:02:52 UTC
[jira] Created: (AMQ-1946) Negative ConsumerCount
Negative ConsumerCount
----------------------
Key: AMQ-1946
URL: https://issues.apache.org/activemq/browse/AMQ-1946
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.1.0
Environment: ActiveMQ 5.1
Reporter: Joe Fernandez
Priority: Minor
Here's the scenario.
You have one or more active consumers for a particular queue.
Via the JConsole, you invoke the DestinationView's resetStatistics() method for that queue
The consumer count is reset to 0, even though you still have one or more active consumers
If you shutdown the consumers and then refresh the 'Attributes' panel for the queue, you end up with a negative value for the ConsumerCount attribute.
The negative number reflects the number of once active consumers. So if you had 2 consumers, you'll see -2.
If you then restart the consumers, the negative value is increased by the number of active consumers thus leaving you with an invalid consumer count. So if you previously had 2 consumers, when you bring 2 back up you'll end up with a 0 value for the ConsumerCount
This probably also holds true for the ProducerCount.
The resetStatistics() method shouldn't reset these two counts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-1946) Negative ConsumerCount
Posted by "Joe Fernandez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Fernandez updated AMQ-1946:
-------------------------------
Attachment: DestinationStatistics.patch
I've attached a patch for review.
> Negative ConsumerCount
> ----------------------
>
> Key: AMQ-1946
> URL: https://issues.apache.org/activemq/browse/AMQ-1946
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: ActiveMQ 5.1
> Reporter: Joe Fernandez
> Priority: Minor
> Attachments: DestinationStatistics.patch
>
>
> Here's the scenario.
> You have one or more active consumers for a particular queue.
> Via the JConsole, you invoke the DestinationView's resetStatistics() method for that queue
> The consumer count is reset to 0, even though you still have one or more active consumers
> If you shutdown the consumers and then refresh the 'Attributes' panel for the queue, you end up with a negative value for the ConsumerCount attribute.
> The negative number reflects the number of once active consumers. So if you had 2 consumers, you'll see -2.
> If you then restart the consumers, the negative value is increased by the number of active consumers thus leaving you with an invalid consumer count. So if you previously had 2 consumers, when you bring 2 back up you'll end up with a 0 value for the ConsumerCount
> This probably also holds true for the ProducerCount.
> The resetStatistics() method shouldn't reset these two counts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1946) Negative ConsumerCount
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1946.
-----------------------------
Fix Version/s: 5.3.0
Resolution: Fixed
Fixed by SVN revision 697937
> Negative ConsumerCount
> ----------------------
>
> Key: AMQ-1946
> URL: https://issues.apache.org/activemq/browse/AMQ-1946
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: ActiveMQ 5.1
> Reporter: Joe Fernandez
> Assignee: Rob Davies
> Priority: Minor
> Fix For: 5.3.0
>
> Attachments: DestinationStatistics.patch
>
>
> Here's the scenario.
> You have one or more active consumers for a particular queue.
> Via the JConsole, you invoke the DestinationView's resetStatistics() method for that queue
> The consumer count is reset to 0, even though you still have one or more active consumers
> If you shutdown the consumers and then refresh the 'Attributes' panel for the queue, you end up with a negative value for the ConsumerCount attribute.
> The negative number reflects the number of once active consumers. So if you had 2 consumers, you'll see -2.
> If you then restart the consumers, the negative value is increased by the number of active consumers thus leaving you with an invalid consumer count. So if you previously had 2 consumers, when you bring 2 back up you'll end up with a 0 value for the ConsumerCount
> This probably also holds true for the ProducerCount.
> The resetStatistics() method shouldn't reset these two counts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1946) Negative ConsumerCount
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1946:
-------------------------------
Assignee: Rob Davies
> Negative ConsumerCount
> ----------------------
>
> Key: AMQ-1946
> URL: https://issues.apache.org/activemq/browse/AMQ-1946
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: ActiveMQ 5.1
> Reporter: Joe Fernandez
> Assignee: Rob Davies
> Priority: Minor
> Attachments: DestinationStatistics.patch
>
>
> Here's the scenario.
> You have one or more active consumers for a particular queue.
> Via the JConsole, you invoke the DestinationView's resetStatistics() method for that queue
> The consumer count is reset to 0, even though you still have one or more active consumers
> If you shutdown the consumers and then refresh the 'Attributes' panel for the queue, you end up with a negative value for the ConsumerCount attribute.
> The negative number reflects the number of once active consumers. So if you had 2 consumers, you'll see -2.
> If you then restart the consumers, the negative value is increased by the number of active consumers thus leaving you with an invalid consumer count. So if you previously had 2 consumers, when you bring 2 back up you'll end up with a 0 value for the ConsumerCount
> This probably also holds true for the ProducerCount.
> The resetStatistics() method shouldn't reset these two counts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.