You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/09/21 18:09:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16623982#comment-16623982 ]
ASF GitHub Bot commented on ARTEMIS-1747:
-----------------------------------------
GitHub user michaelandrepearce opened a pull request:
https://github.com/apache/activemq-artemis/pull/2326
ARTEMIS-1747 - 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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/michaelandrepearce/activemq-artemis ARTEMIS-1747-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2326.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2326
----
----
> 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.6.0
>
>
> 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)