You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Alexander (Jira)" <ji...@apache.org> on 2023/04/03 09:42:00 UTC
[jira] [Created] (ARTEMIS-4232) Broker deadlock occurs when restarting another broker Linked
Alexander created ARTEMIS-4232:
----------------------------------
Summary: Broker deadlock occurs when restarting another broker Linked
Key: ARTEMIS-4232
URL: https://issues.apache.org/jira/browse/ARTEMIS-4232
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker
Affects Versions: 2.19.1
Environment: {code:java}
// code placeholder
{code}
Reporter: Alexander
Continuation: https://issues.apache.org/jira/browse/ARTEMIS-4114
Broker deadlock occurs when restarting another broker, which is connected to the one that has fallen through the bridge.
When one of the brokers is restarted (a cluster of 4 brokers), we get a restart of a broker located in another cluster (clusters are connected via a bridge).
Configuration:
2 clusters:
1) ART.GW.CLS1, ART.GW.CLS2, ART.GW.CLS3, ART.GW.CLS4
2) ART.EL.CLS1, ART.EL.CLS2, ART.EL.CLS3, ART.EL.CLS4
In every cluster brokers are connected via staticConnectors, scaleDown policy is also configured, bridges:
<ha-policy> <live-only> <scale-down> <connectors> <connector-ref>ART.GW.CLS1-connector</connector-ref> <connector-ref>ART.GW.CLS2-connector</connector-ref><connector-ref>ART.GW.CLS3-connector</connector-ref> </connectors> </scale-down> </live-only> </ha-policy>
...
<bridges>
<bridge name="ART.EL.CLS">
<queue-name>ART.EL.CLS</queue-name>
<forwarding-address>ART.EL.CLS</forwarding-address>
<reconnect-attempts>-1</reconnect-attempts>
<static-connectors>
<connector-ref>ART.EL.CLS1-connector</connector-ref>
<connector-ref>ART.EL.CLS2-connector</connector-ref>
<connector-ref>ART.EL.CLS3-connector</connector-ref>
<connector-ref>ART.EL.CLS4-connector</connector-ref>
</static-connectors>
</bridge>
<bridges>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)