You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2020/11/23 19:52:00 UTC

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

     [ https://issues.apache.org/jira/browse/ARTEMIS-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram reassigned ARTEMIS-3008:
---------------------------------------

    Assignee: Justin Bertram

> 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
>
> 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)