[ 
https://issues.apache.org/jira/browse/ARTEMIS-4527?focusedWorklogId=901798&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-901798
 ]

ASF GitHub Bot logged work on ARTEMIS-4527:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jan/24 21:49
            Start Date: 25/Jan/24 21:49
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on PR #4705:
URL: 
https://github.com/apache/activemq-artemis/pull/4705#issuecomment-1911053851

   @AntonRoskvist can you try my branch with a commit I added?
   
   
   I can't make these tests to run.  Even on my biggest CI.
   
   
   I tried adapting your test on my branch, to not require UDP.
   
   And one of the issues I see is that the threads keep being created on 
Spring. So I used an Executor to limit some of that.
   
   But still the container won't be stopped in case of any issues in the test 
(leaking threads onward).
   
   
   to try my branch:
   
   
   ```
   git remote add clebert https://github.com/clebertsuconic/activemq-artemis.git
   git fetch clebert
   git checkout clebert/ARTEMIS-4527 -B any-local-name-you-like
   ```
   
   
   on this commit I'm also not using your template, and using broker-properties 
to set the address-settings.
   
   
   Let me know if you can help me figure out this one please? you can reach me 
on slack if you prefer.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 901798)
    Time Spent: 4.5h  (was: 4h 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: 4.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)

Reply via email to