[
https://issues.apache.org/jira/browse/ARTEMIS-4642?focusedWorklogId=904806&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-904806
]
ASF GitHub Bot logged work on ARTEMIS-4642:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Feb/24 00:10
Start Date: 14/Feb/24 00:10
Worklog Time Spent: 10m
Work Description: tabish121 opened a new pull request, #4819:
URL: https://github.com/apache/activemq-artemis/pull/4819
…blocked
Under some scenarios federation demand tracking is losing track of total
demand for a federated resource leading to teardown of federated links before
all local demand has been removed from the resource. This occurs most often if
the attempts to establish a federation link are refused because the resource
hasn't yet been created and an eventual attach succeeds, but can also occur in
combination with a plugin blocking or not blocking federation link creation in
some cases.
Issue Time Tracking
-------------------
Worklog Id: (was: 904806)
Remaining Estimate: 0h
Time Spent: 10m
> AMQP Federation demand tracking can under count demand in some narrow cases
> ---------------------------------------------------------------------------
>
> Key: ARTEMIS-4642
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4642
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.32.0
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Minor
> Fix For: 2.33.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In some narrow cases the AMQP federation demand tracking can under count the
> demand on an address or queue and should track more closely the current
> demand regardless of a federation link being active.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
