[
https://issues.apache.org/jira/browse/ARTEMIS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360848#comment-15360848
]
Lionel Cons commented on ARTEMIS-601:
-------------------------------------
Justin, this is the first time I read about "Artemis' new XML format". Is this
documented/discussed somewhere?
Of course, management tools could be extended with scripts talking JMX that try
to find the differences between the expected configuration and the existing
configuration and fire up the the right API calls. This however would move the
complexity from one place (the broker) to multiple places (all the various
management tools used in the wild). Instead of having one single
implementation, evolving along with the broker, we would have different
implementations, each with their own set of bugs, that all need to be kept in
sync with changes in the broker.
ActiveMQ's approach (periodically reload the configuration file) is far
superior and goes beyond only security settings. It would be a pity to lease
this feature in Artemis.
> 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)
