[
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 issues were multiple connections are setup to the same cluster node
after a uncontrolled node failure. This resulted in a different node having two
connections setup to that failed one.
This is reproducible using docker by setting up a static cluster connection
with two nodes (artemis-0 & artemis-1) and running "docker rm -f artemis-1".
After restarting artemis-1, artemis-0 has two cluster connection to artemis-1.
This is the configuration for artemis-0, artemis-1 is the same but different
connector-ref.
{code:java}
<connectors>
<connector name="artemis-0">tcp://artemis-0:61617</connector>
<connector name="artemis-1">tcp://artemis-1:61617</connector>
</connectors>
<cluster-connections>
<cluster-connection name="artemis">
<address>iot,test</address>
<connector-ref>artemis-0</connector-ref>
<retry-interval>1000</retry-interval>
<retry-interval-multiplier>2</retry-interval-multiplier>
<max-retry-interval>60000</max-retry-interval>
<initial-connect-attempts>-1</initial-connect-attempts>
<reconnect-attempts>3</reconnect-attempts>
<use-duplicate-detection>true</use-duplicate-detection>
<message-load-balancing>ON_DEMAND</message-load-balancing>
<max-hops>1</max-hops>
<static-connectors allow-direct-connections-only="true">
<connector-ref>artemis-1</connector-ref>
</static-connectors>
</cluster-connection>
</cluster-connections>{code}
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 they can be stopped, but that doesn't solve the
issue.
was:
We have issues were multiple connections are setup to the same cluster node
after a uncontrolled node failure. This resulted in a different node having two
connections setup to that failed one.
This is reproducible using docker by setting up a static cluster connection
with two nodes (artemis-0 & artemis-1) and running "docker rm -f artemis-1".
After restarting artemis-1, artemis-0 has two cluster connection to artemis-1.
{code:java}
<connectors> <connector
name="artemis-0">tcp://artemis-0:61617</connector> <connector
name="artemis-1">tcp://artemis-1:61617</connector> </connectors>
<cluster-connections> <cluster-connection name="artemis">
<address>iot,test</address> <connector-ref>HOSTNAME</connector-ref>
<retry-interval>1000</retry-interval>
<retry-interval-multiplier>2</retry-interval-multiplier>
<max-retry-interval>60000</max-retry-interval>
<initial-connect-attempts>-1</initial-connect-attempts>
<reconnect-attempts>3</reconnect-attempts>
<use-duplicate-detection>true</use-duplicate-detection>
<message-load-balancing>ON_DEMAND</message-load-balancing>
<max-hops>1</max-hops> <static-connectors
allow-direct-connections-only="true">
<connector-ref>artemis-0</connector-ref>
<connector-ref>artemis-1</connector-ref> </static-connectors>
</cluster-connection> </cluster-connections>{code}
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 they can be stopped, but that doesn't solve the
issue.
> 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 issues were multiple connections are setup to the same cluster node
> after a uncontrolled node failure. This resulted in a different node having
> two connections setup to that failed one.
> This is reproducible using docker by setting up a static cluster connection
> with two nodes (artemis-0 & artemis-1) and running "docker rm -f artemis-1".
> After restarting artemis-1, artemis-0 has two cluster connection to artemis-1.
> This is the configuration for artemis-0, artemis-1 is the same but different
> connector-ref.
> {code:java}
> <connectors>
> <connector name="artemis-0">tcp://artemis-0:61617</connector>
> <connector name="artemis-1">tcp://artemis-1:61617</connector>
> </connectors>
> <cluster-connections>
> <cluster-connection name="artemis">
> <address>iot,test</address>
> <connector-ref>artemis-0</connector-ref>
> <retry-interval>1000</retry-interval>
> <retry-interval-multiplier>2</retry-interval-multiplier>
> <max-retry-interval>60000</max-retry-interval>
> <initial-connect-attempts>-1</initial-connect-attempts>
> <reconnect-attempts>3</reconnect-attempts>
> <use-duplicate-detection>true</use-duplicate-detection>
> <message-load-balancing>ON_DEMAND</message-load-balancing>
> <max-hops>1</max-hops>
> <static-connectors allow-direct-connections-only="true">
> <connector-ref>artemis-1</connector-ref>
> </static-connectors>
> </cluster-connection>
> </cluster-connections>{code}
> 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 they can be stopped, but that doesn't solve the
> issue.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
