[
https://issues.apache.org/jira/browse/ARTEMIS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357754#comment-15357754
]
Justin Bertram commented on ARTEMIS-601:
----------------------------------------
To be clear, the security-settings can be changed at runtime via the management
API (e.g {{ActiveMQServerControl#addSecuritySettings}},
{{ActiveMQServerControl#removeSecuritySettings}}). The management API is
available through JMX so traditional JMX clients (e.g. JConsole, JVisualVM,
etc.) can make changes as well as script-based clients (e.g. via Jmx4Perl,
Jmx4py). The management API is available through REST as well which opens the
door for HTTP clients (e.g. curl). My point here is that there's lots of ways
to change the configuration during runtime.
That said, those changes don't persist so when the broker is restarted they are
lost. ARTEMIS-66 is already open for persisting configuration changes done via
the management API. If ARTEMIS-66 was resolved and given the options for the
management API would that fulfill your functional requirement or is it absolute
necessary for you to modify the XML itself?
> 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)
