[
https://issues.apache.org/jira/browse/ARTEMIS-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817739#comment-17817739
]
ASF subversion and git services commented on ARTEMIS-4642:
----------------------------------------------------------
Commit b8800337df4b2e9a7ab7fde42a1a0bd8c342a6ba in activemq-artemis's branch
refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=b8800337df ]
ARTEMIS-4642 Fix tracked federated demand when links are rejected or 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.
> 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: 0.5h
> 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)
