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

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

                Author: ASF GitHub Bot
            Created on: 23/Sep/24 15:49
            Start Date: 23/Sep/24 15:49
    Worklog Time Spent: 10m 
      Work Description: jbertram opened a new pull request, #5246:
URL: https://github.com/apache/activemq-artemis/pull/5246

   
   
   Throwing an exception when clearing the bindings when a cluster-connection 
is closed short-circuits the clearing (and closing) process. This commit fixes 
that by simply logging the failure to clear and continues on.
   
   No new tests are added with this commit. It relies on existing tests.




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

            Worklog Id:     (was: 935888)
    Remaining Estimate: 0h
            Time Spent: 10m

> The load balancing is not working correctly when several brokers are down
> -------------------------------------------------------------------------
>
>                 Key: ARTEMIS-5042
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5042
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Balancer
>    Affects Versions: 2.35.0
>         Environment: Cluster Configuration broker.xml:
>  
> <cluster-connections>
>          <cluster-connection name="mccon">
>         <connection-ttl>60000</connection-ttl>
>             <call-timeout>5000</call-timeout>
>             <retry-interval>500</retry-interval>
>             <retry-interval-multiplier>1.0</retry-interval-multiplier>
>             <max-retry-interval>5000</max-retry-interval>
>             <initial-connect-attempts>-1</initial-connect-attempts>
>             <reconnect-attempts>-1</reconnect-attempts>
>     <forward-when-no-consumers>false</forward-when-no-consumers>    
>             <connector-ref>artemis</connector-ref>
>             <message-load-balancing>ON_DEMAND</message-load-balancing>
>             <max-hops>1</max-hops>
>             <static-connectors>
>                <connector-ref>node0</connector-ref>
>                <connector-ref>node1</connector-ref>
>                <connector-ref>node2</connector-ref>
>  
>             </static-connectors>
>          </cluster-connection>
>       </cluster-connections>
>            Reporter: Juanjo Marin
>            Assignee: Justin Bertram
>            Priority: Major
>         Attachments: 1NodoUp.PNG, 1nodeUp.PNG, 3NodesUp.PNG, 3Nodosup.PNG, 
> ArtemisInternalWithMessage.PNG, EmptysQueue.PNG, 
> QueueInternWithMessageNoConsumer.PNG, artemis.log, broker.xml
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The load balancing is not working correctly when several brokers are down. 
> With the configuration we have in the cluster, we understand that this should 
> not be happening. The load balancing should be smart and not send messages to 
> the nodes that are down."



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to