[
https://issues.apache.org/jira/browse/ARTEMIS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363831#comment-15363831
]
Lionel Cons commented on ARTEMIS-601:
-------------------------------------
Our tools already generate Artemis' XML.
What I mean by "find the differences between the expected configuration and
the existing configuration and fire up the the right API calls" is exactly what
you wrote later on "look at the XML and see what changes needed to be made,
make a management API call to make the necessary change". Rather than every
Artemis user having to implement tools to "see what changes needed to be made,
make a management API call to make the necessary change", it would be much
better to have this logic inside Artemis so every Artemis user would only have
to write the expected XML file.
> 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)
