[
https://issues.apache.org/jira/browse/ARTEMIS-4626?focusedWorklogId=903043&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-903043
]
ASF GitHub Bot logged work on ARTEMIS-4626:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/Feb/24 13:59
Start Date: 01/Feb/24 13:59
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4797:
URL:
https://github.com/apache/activemq-artemis/pull/4797#issuecomment-1921391678
this looks good to me.
I have one question about the HashSet used but it's purely a question for my
understanding.. not asking any changes.
Issue Time Tracking
-------------------
Worklog Id: (was: 903043)
Time Spent: 40m (was: 0.5h)
> AMQP Federation demand tracking can overcount demand
> ----------------------------------------------------
>
> Key: ARTEMIS-4626
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4626
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.32.0
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The demand tracking for Address bindings and Queue consumers that controls
> when a federation consumer is created and destroyed can race on start of
> federation with consumers or bindings being added and removed and over count
> the demand leading to the federation consumers not being shutdown when demand
> on the local broker drops to zero. A better mechanism of tracking needs to
> be added to make demand tracking idempotent for additions and removals of
> local demand and the startup demand checks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
