[
https://issues.apache.org/jira/browse/ARTEMIS-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Månsson updated ARTEMIS-3602:
------------------------------------
Affects Version/s: 2.18.0
> Cluster connection not distribution messages
> --------------------------------------------
>
> Key: ARTEMIS-3602
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3602
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.18.0
> Reporter: Tobias Månsson
> Priority: Major
>
> The cluster is set up as a ON_DEMAND cluster with two nodes, were only one
> node is exposed to the external load-balancer and receiving new connections.
> This creates a online failover setup by switching over new connections to the
> other node, before taking down the current for maintenance.
> During one deployment, the active broker node was failed over without
> shutting down the passive node. This left the current connection on the
> passive node, while new connections were created against the now active one.
> If message were sent to the now passive node, they were synchronized
> correctly to both nodes and to all connections. But if the messages were sent
> to then now active node (the intended behavior), they were not sent to
> clients currently connected to the now passive node.
> The logs and message counters confirm this, but no cause has been found.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
