[
https://issues.apache.org/jira/browse/ARTEMIS-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Månsson updated ARTEMIS-3742:
------------------------------------
Description:
We have a process were we use the same hostname for cluster nodes as part of
node upgrades.
This is not ideal, and we are working to change it.
We've had issues now though were multiple connections are setup to the same
cluster node, one per physical host with the same hostname. This is probably to
be expected, but what was not expected was that the connections persisted after
the old node was taken down. This resulted in a different node having two
connections setup, but both to the same physical node.
This caused issues with queue binding in the form of AMQ224037 errors.
Is this expected to occur? Can cluster connections be removed trough the
management api? I only found that can be stopped.
was:
We have a process were we use the same hostname for cluster nodes as part of
node upgrades.
This is not ideal, and we are working to change it.
We've had issues now though were multiple connections are setup to the same
cluster node, one per physical host with the same hostname. This is probably to
be expected, but what was not expected was that the connections persisted after
the old node was taken down. This resulted in a different node having to
connections setup, but both to the same physical node.
This caused issues with queue binding in the form of AMQ224037 errors.
Is this expected to occur? Can cluster connections be removed trough the
management api? I only found that can be stopped.
> Multiple cluster connections are made to the same cluster node
> --------------------------------------------------------------
>
> Key: ARTEMIS-3742
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3742
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Tobias Månsson
> Priority: Major
>
> We have a process were we use the same hostname for cluster nodes as part of
> node upgrades.
> This is not ideal, and we are working to change it.
> We've had issues now though were multiple connections are setup to the same
> cluster node, one per physical host with the same hostname. This is probably
> to be expected, but what was not expected was that the connections persisted
> after the old node was taken down. This resulted in a different node having
> two connections setup, but both to the same physical node.
> This caused issues with queue binding in the form of AMQ224037 errors.
> Is this expected to occur? Can cluster connections be removed trough the
> management api? I only found that can be stopped.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
