[
https://issues.apache.org/jira/browse/ARTEMIS-4527?focusedWorklogId=894755&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-894755
]
ASF GitHub Bot logged work on ARTEMIS-4527:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Dec/23 16:59
Start Date: 08/Dec/23 16:59
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4705:
URL:
https://github.com/apache/activemq-artemis/pull/4705#issuecomment-1847526576
Do you have any insight into how/why the `CONSUMER_CREATED` notification is
being sent before the `BINDING_ADDED`? Theoretically the `BINDING_ADDED` should
always be sent before the `CONSUMER_CREATED` even if they are done in different
threads since any operation should block waiting for the `createQueue` to
return before continuing on to create the consumer.
Issue Time Tracking
-------------------
Worklog Id: (was: 894755)
Time Spent: 40m (was: 0.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: 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)
