[
https://issues.apache.org/jira/browse/ARTEMIS-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628792#comment-16628792
]
ASF GitHub Bot commented on ARTEMIS-2094:
-----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/2326
@michaelandrepearce can you do the cherry-pick on 2.6.x? there are
conflicts.. on such cases I usually ask the committer to do the cherry-pick.
on 2.6.x the code was changed around LegacyJMSConfiguration.
Can you please still refer commit cce0e1927c258ce6f3c3c3cb0d90bad5337b7d12
once you send your PR or the commit directly? I have written a report generator
to correlate these XREFs and make sure we won't miss them.
> 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)
