[jira] [Commented] (ARTEMIS-3008) Configuration reload triggered by Management API

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271627#comment-17271627 ] 

ASF subversion and git services commented on ARTEMIS-3008:
----------------------------------------------------------

Commit 4fbc8bf67db427a66d3c55eaf83f661618872dcb in activemq-artemis's branch refs/heads/master from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=4fbc8bf ]

ARTEMIS-3008 mngmnt op to reload config file


> Configuration reload triggered by Management API
> ------------------------------------------------
>
>                 Key: ARTEMIS-3008
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3008
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Apache Dev
>            Assignee: Justin Bertram
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> For systems where configuration auto-reload is disabled, it would be useful to have a broker management API triggering the reload of configurations.
> This would also be beneficial for configuration files included in {{broker.xml}}, which are not currently monitored (see ARTEMIS-1922),  as "touch"ing {{broker.xml}} could be replaced by a more high-level approach (i.e. management function invocation).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)