You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Apache Dev (Jira)" <ji...@apache.org> on 2021/07/05 15:44:00 UTC

[jira] [Updated] (ARTEMIS-3377) Client does not reconnect after failover when both Live and Backup brokers are killed

     [ https://issues.apache.org/jira/browse/ARTEMIS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Apache Dev updated ARTEMIS-3377:
--------------------------------
    Affects Version/s: 2.16.0

> Client does not reconnect after failover when both Live and Backup brokers are killed
> -------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3377
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3377
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.16.0
>            Reporter: Apache Dev
>            Priority: Major
>
> Scenario:
>  * 3 brokers configured in Live/Backup with shared DB storage
>  ** Broker A is "Live"
>  ** Broker B is "Backup Announced"
>  ** Broker C is "Waiting to become backup node"
>  * Client is connected using the following HA URL:
>  ** (tcp://activemq:61616,tcp://activemq2:61616,tcp://activemq3:61616)?ha=true&reconnectAttempts=-1&initialConnectAttempts=-1&consumerWindowSize=1048576&minLargeMessageSize=2147483647
>  * Both Broker A and Broker B are killed
>  * Broker C becomes Live
>  * Client does not reconnect to Broker C automatically even if configured with "reconnectAttempts=-1"
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)