You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2018/08/20 16:58:00 UTC

[jira] [Closed] (ARTEMIS-2032) Artemis RA connections disconnected after failover

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

clebert suconic closed ARTEMIS-2032.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.3
                   2.7.0

> Artemis RA connections disconnected after failover
> --------------------------------------------------
>
>                 Key: ARTEMIS-2032
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2032
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Martyn Taylor
>            Priority: Major
>             Fix For: 2.7.0, 2.6.3
>
>
> This was tested within the WF application server.  It was discovered that the RA does note fail over from live to backup under certain scenarios: 
> Backup activates after a fail over, the RA does not reconnect to that backup.
> Test scenario:
> These tests are using the Artemis RA within the WF application server.
>  * There are three servers. Live server (Node 1) and backup server (Node 2) are in dedicated HA topology.
>  * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server.
>  * When all messages are sent, deploy message driven bean on Node 3.
>  * MDB sends messages form InQueue to OutQueue.
>  * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup.
>  * Receive messages from OutQueue from live server.
> Results:
> After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)