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 2019/01/18 02:21:08 UTC
[jira] [Closed] (ARTEMIS-2094) Configuration change loss after
failover to slave
[ https://issues.apache.org/jira/browse/ARTEMIS-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
clebert suconic closed ARTEMIS-2094.
------------------------------------
> Configuration change loss after failover to slave
> -------------------------------------------------
>
> Key: ARTEMIS-2094
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2094
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.6.3
> Reporter: Michael Andre Pearce
> Assignee: Michael Andre Pearce
> Priority: Major
> Fix For: 2.7.0
>
>
> This is further cases discovered during testing network failures.
> Essentially we have noticed when config settings are reloaded such as address-setting or security-setting, the live node correctly reloads, but after live failure the backup activates, the backup does not contain these changes due to the configuration object held inside ActiveMQServerImpl is out of date to when the backup server first started.
> so further enhancements/bug fixes on top of ARTEMIS-1747 - Fix Configuration change loss when network Issue. which fixed this for an active node. Essentially we just need to keep the updating of the configuration object in ActiveMQServerImpl outside the isActive check.
> Also address-settings and security settings should be swap'd during initialisation phase 2, so these are set to latest config after activation.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)