[
https://issues.apache.org/jira/browse/ARTEMIS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358420#comment-15358420
]
Lionel Cons commented on ARTEMIS-601:
-------------------------------------
Our brokers have frequent security settings changes. With ActiveMQ 5.x, this is
very easy: simply change the {{activemq.xml}} file and the change will be taken
into account a few seconds later. Since the configuration file is the master, a
restart of the broker maintains these security settings.
Changing the security settings via JMX would require much more work for us and
leave us with a runtime configuration different from the configuration file. We
do not want/need ARTEMIS-66's configuration persistence. Our brokers, like
almost all our services, are configured via configuration files managed with
ad-hoc tools such as Puppet. It much easier to make sure the configuration
files are what they should rather than using service-specific API (JMX,
REST...) to alter the runtime configurations.
> Add support for automatic configuration reloading
> -------------------------------------------------
>
> Key: ARTEMIS-601
> URL: https://issues.apache.org/jira/browse/ARTEMIS-601
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Lionel Cons
> Assignee: Justin Bertram
>
> ActiveMQ 5.x does support automatic configuration reloading and this includes
> security related configuration (amongst other things), see
> http://activemq.apache.org/runtime-configuration.html.
> In our environment, it is very important to change the security settings
> without having to restart the broker.This works fine with ActiveMQ 5.x and
> the {{runtimeConfigurationPlugin}}.
> ARTEMIS-579 clarified the reload of the JAAS files. This is good but it is
> only one half of the security related configuration since the rest appears in
> {{<security-settings>}}.
> Could Artemis please also implement automatic configuration reloading, at
> least for the security configuration?
> Of course, the more settings can be changed without restarting the broker,
> the better...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
