[
https://issues.apache.org/jira/browse/ARTEMIS-5042?focusedWorklogId=935922&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-935922
]
ASF GitHub Bot logged work on ARTEMIS-5042:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Sep/24 19:12
Start Date: 23/Sep/24 19:12
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #5246:
URL: https://github.com/apache/activemq-artemis/pull/5246#discussion_r1771953251
##########
artemis-server/src/main/java/org/apache/activemq/artemis/core/server/ActiveMQServerLogger.java:
##########
@@ -1621,4 +1621,7 @@ void
noQueueIdDefined(org.apache.activemq.artemis.api.core.Message message,
@LogMessage(id = 224139, value = "Failed to stop bridge: {}", level =
LogMessage.Level.ERROR)
void errorStoppingBridge(String bridgeName, Exception e);
+
+ @LogMessage(id = 224140, value = "Clearing bindings on cluster-connection
{} failed to remove binding {}: {}", level = LogMessage.Level.WARN)
+ void clusterConnectionFailedToRemovingBindingOnClear(String
clusterConnection, String binding, String exceptionMessage);
Review Comment:
Fixed.
Issue Time Tracking
-------------------
Worklog Id: (was: 935922)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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
