[
https://issues.apache.org/jira/browse/ARTEMIS-1982?focusedWorklogId=258799&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-258799
]
ASF GitHub Bot logged work on ARTEMIS-1982:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Jun/19 15:03
Start Date: 12/Jun/19 15:03
Worklog Time Spent: 10m
Work Description: jbertram commented on pull request #2700: ARTEMIS-1982
queue metrics can go negative
URL: https://github.com/apache/activemq-artemis/pull/2700
When redelivery is exhausted and messages are sent to a DLA with bindings
then some queue metrics can go negative.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 258799)
Time Spent: 10m
Remaining Estimate: 0h
> Queue#MessageCount negative and messages stop flowing to AMQP consumer
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-1982
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1982
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.5.0, 2.6.2
> Reporter: Keith Wall
> Priority: Major
> Attachments: ARTEMIS-1982.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I am running performance tests against EnMasse which currently uses Artemis
> 2.5.0. Many millions of messages have traversed the Broker (all AMQP
> protocol).
>
> I have encountered a situation where messages have stopped flowing to the
> AMQP consumer. On inspection of the Artemis console, I notice that
> statistics including the MessageCount have gone negative (-99). One in this
> state, I notice if I produce one message then attach a consumer, no message
> flows. However if add two messages to the queue, the consumer gets only the
> 2nd message. The first message is seemingly lost.
> I've seen this situation once.
>
> bash-4.2$ curl --user admin:admin -k
> [https://localhost:8161/console/jolokia/read/org.apache.activemq.artemis:broker=%22broker-0%22,component=addresses,address=%22queue%22,subcomponent=queues,routing-type=%22anycast%22,queue=%22queue%22]
>
> {code:javascript}
> {
> "request": {
> "mbean":
> "org.apache.activemq.artemis:address=\"queue\",broker=\"broker-0\",component=addresses,queue=\"queue\",routing-type=\"anycast\",subcomponent=queues",
> "type": "read"
> },
> "value": {
> "User": "null",
> "MaxConsumers": -1,
> "Address": "queue",
> "Exclusive": false,
> "PurgeOnNoConsumers": false,
> "DurableDeliveringSize": 0,
> "PersistentSize": -68112,
> "ScheduledCount": 0,
> "MessagesKilled": 99,
> "Name": "queue",
> "DurableScheduledCount": 0,
> "DurableMessageCount": 0,
> "ExpiryAddress": null,
> "ID": 6,
> "FirstMessageAsJSON": "[{}]",
> "RoutingType": "ANYCAST",
> "Paused": false,
> "DurableDeliveringCount": 0,
> "FirstMessageAge": null,
> "DeadLetterAddress": "DLQ",
> "DurablePersistentSize": 0,
> "MessagesAdded": 39470041,
> "ConsumerCount": 1,
> "DeliveringCount": -99,
> "MessagesAcknowledged": 39469942,
> "MessagesExpired": 0,
> "DeliveringSize": -68112,
> "LastValue": false,
> "Temporary": false,
> "FirstMessageTimestamp": null,
> "Filter": null,
> "ScheduledSize": 0,
> "Durable": true,
> "DurableScheduledSize": 0,
> "MessageCount": -99
> },
> "timestamp": 1532007015,
> "status": 200
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
