[
https://issues.apache.org/jira/browse/ARTEMIS-4527?focusedWorklogId=901479&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-901479
]
ASF GitHub Bot logged work on ARTEMIS-4527:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jan/24 15:04
Start Date: 24/Jan/24 15:04
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4705:
URL:
https://github.com/apache/activemq-artemis/pull/4705#issuecomment-1908314543
@jbertram
You are correct. I actually tried this at first but got issues with
deadlocking because of calls to addBinding() from `PostOffice#onNotification`,
then I did not try it again after having those calls go directly to the
`addressManager`. Thanks!
During testing of this though, I saw the problem yet again... it's much less
of an issue after the synchronization but can still happen apparently. I
narrowed it down to varying delays in `PostOffice#processRoute()`... don't know
if my fix for that is okay though but I figured if all references are
nonDurables the call to `storageManager.afterCompleteOperations()` would not be
necessary, is that right? Have not seen the issue since at least.
Issue Time Tracking
-------------------
Worklog Id: (was: 901479)
Time Spent: 1h 40m (was: 1.5h)
> 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: 1h 40m
> 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)
