[ https://issues.apache.org/jira/browse/ARTEMIS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410404#comment-15410404 ]
ASF GitHub Bot commented on ARTEMIS-601: ---------------------------------------- GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/703 ARTEMIS-601 + logger fixes You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-601 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/703.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #703 ---- commit 85857ab8eb1b1eca2498306239740e0e39d2acd4 Author: jbertram <jbert...@apache.org> Date: 2016-08-04T21:23:59Z Fix improper IDs in logger commit 6d7e1f92aeb807c5234638519fdce456834cc9c3 Author: jbertram <jbert...@apache.org> Date: 2016-08-03T22:27:26Z ARTEMIS-601 load runtime security cfg file changes ---- > 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)