You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/11/24 17:00:03 UTC
[jira] [Work logged] (ARTEMIS-3008) Configuration reload triggered
by Management API
[ https://issues.apache.org/jira/browse/ARTEMIS-3008?focusedWorklogId=516248&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-516248 ]
ASF GitHub Bot logged work on ARTEMIS-3008:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Nov/20 16:59
Start Date: 24/Nov/20 16:59
Worklog Time Spent: 10m
Work Description: jbertram opened a new pull request #3358:
URL: https://github.com/apache/activemq-artemis/pull/3358
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 516248)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)