[
https://issues.apache.org/jira/browse/AMQ-9420?focusedWorklogId=901223&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-901223
]
ASF GitHub Bot logged work on AMQ-9420:
---------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/24 15:33
Start Date: 23/Jan/24 15:33
Worklog Time Spent: 10m
Work Description: cshannon commented on PR #1142:
URL: https://github.com/apache/activemq/pull/1142#issuecomment-1906316401
This is a pretty simple and straight forward change so I'm going to merge
(the majority of code is testing updates) and backport. I will keep an eye on
the full CI builds
Issue Time Tracking
-------------------
Worklog Id: (was: 901223)
Time Spent: 1h 10m (was: 1h)
> KahaDB durable subscription stats can go negative on duplicate acks
> -------------------------------------------------------------------
>
> Key: AMQ-9420
> URL: https://issues.apache.org/jira/browse/AMQ-9420
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.18.3, 6.0.1
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 6.1.0, 5.18.4, 5.17.7, 6.0.2
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> AMQ-6375 added support for non blocking durable subscription statistics to
> KahaDB to track pending message count and message size metrics. By default
> this is disabled and can be enabled with the enableSubscriptionStatistics
> flag on KahaDB.
> On rare occasions I have noticed that sometimes the metrics may got negative
> or be slightly off. I found an area where it's possible if a duplicate ack
> comes in then in some scenarios the metrics may be deprecated twice. This
> issue only applies to the subscription stats and not the store statistics for
> the overall destination as those stats would only get decremented once when
> the message is removed from the order index.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
