[
https://issues.apache.org/jira/browse/ARTEMIS-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628776#comment-16628776
]
ASF subversion and git services commented on ARTEMIS-2094:
----------------------------------------------------------
Commit cce0e1927c258ce6f3c3c3cb0d90bad5337b7d12 in activemq-artemis's branch
refs/heads/master from [~teaandcoffee]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=cce0e19 ]
ARTEMIS-2094 - Fix Configuration change loss when network Issue
Further fix around network loss.
If network loss (split) and slave activates, for a period its config used when
it initializes in initialisePart2 was stale.
Add/Extend test to ensure address-setting change made on live preserved on
slave (after activation)
Add/Extend test to ensure security-setting change made on live preserved on
backup (after activation)
> 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
>
> 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)
