[
https://issues.apache.org/jira/browse/ARTEMIS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363070#comment-15363070
]
Justin Bertram commented on ARTEMIS-601:
----------------------------------------
When I referred to "Artemis' new XML format" I meant in reference to ActiveMQ
5.x. In other words, the XML format that Artemis uses is different (and newer)
than the XML format that 5.x uses. I mentioned this because I assume all your
management tools that currently modify the 5.x XML format will need to be
updated to work with Artemis' new XML format.
I think there might be a communication breakdown somewhere. I don't understand
why your tools will need to "find the differences between the expected
configuration and the existing configuration and fire up the the right API
calls." As I mentioned previously, the current implementation idea for
ARTEMIS-66 is to write changes made via the management API back to the XML - in
real time. In other words, a tool or a user could, for example, look at the
XML and see what changes needed to be made, make a management API call to make
the necessary change, reload the XML and that change would be visible.
Furthermore, I don't understand why complexity in the management tools
themselves would increase necessarily. I would expect the management API and
the XML format to have the same potential for change requiring tool updates.
I do think we'll implement this eventually. What I'm mainly trying to do here
is understand your use-case and offer potential alternatives since it's not
clear when this would be implemented and what priority it takes over other
tasks. Resources are finite, after all.
> 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)
