You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Michael Andre Pearce (JIRA)" <ji...@apache.org> on 2018/03/16 08:40:00 UTC
[jira] [Resolved] (ARTEMIS-1747) When Broker Stops and Starts
configuration changes by reload are lost
[ https://issues.apache.org/jira/browse/ARTEMIS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Andre Pearce resolved ARTEMIS-1747.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.5.1
> When Broker Stops and Starts configuration changes by reload are lost
> ---------------------------------------------------------------------
>
> Key: ARTEMIS-1747
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1747
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Michael Andre Pearce
> Assignee: Michael Andre Pearce
> Priority: Blocker
> Fix For: 2.5.1
>
>
> When the broker is stopped and started (not JVM restart) e.g. by the NetworkHealthChecker when a network is detected unhealthy and then becomes healthy again, the broker looses any configuration changes made by reload.
> address-settings
> security-settings
> addresses
> queues
>
> This seems to be due to initializing step uses the stored configuration object thats created on JVM start, and this is never updated when reloads occur, thus why on start and stop broker configuration is reverted to the state when broker first started.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)