[
https://issues.apache.org/jira/browse/ARTEMIS-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884280#comment-17884280
]
Juanjo Marin commented on ARTEMIS-5042:
---------------------------------------
I see the commit but if needed , way to reproduce:
Initial State : A cluster with 3 statics connected brokers with the attached
configuration (broker.xml). Each node on a different virtual machine.
Step 1 : Kill one or two brokers with kill -9 PID, to simulate a machine or
network failure
Step 2 : Wait until the configured reconnection attempts are exhausted
Step 3: Send messages, in this case with JMS in java 21 aplication with pool
connections for producers ([Pooled JMS 3.1.0
version|https://mvnrepository.com/artifact/org.messaginghub/pooled-jms]).
Step 4 : Check on the Artemis web console whether the internal queues have
messages or not.
We understand that, since we waited for the reconnection attempts to finish,
the messages should not remain in the internal queues but should instead be
processed by the queue of the broker that is running.
> 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: 40m
> 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
