[
https://issues.apache.org/jira/browse/ARTEMIS-4527?focusedWorklogId=901320&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-901320
]
ASF GitHub Bot logged work on ARTEMIS-4527:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jan/24 03:36
Start Date: 24/Jan/24 03:36
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4705:
URL:
https://github.com/apache/activemq-artemis/pull/4705#issuecomment-1907298955
You added `addressLock` and use it inside `removeBinding`, `addBinding`, and
`getBinding`. However, both `removeBinding` and `addBinding` are already
`synchronized`. Therefore, you can just make `getBinding` `synchronized` as
well. This would simplify your PR significantly.
Issue Time Tracking
-------------------
Worklog Id: (was: 901320)
Time Spent: 1.5h (was: 1h 20m)
> Redistributor race when consumerCount reaches 0 in cluster
> ----------------------------------------------------------
>
> Key: ARTEMIS-4527
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4527
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> This is a very rare bug caused by cluster notifications arriving in the wrong
> order in some very specific circumstances
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
