[
https://issues.apache.org/jira/browse/ARTEMIS-4001?focusedWorklogId=809988&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-809988
]
ASF GitHub Bot logged work on ARTEMIS-4001:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 19/Sep/22 10:34
Start Date: 19/Sep/22 10:34
Worklog Time Spent: 10m
Work Description: gtully opened a new pull request, #4222:
URL: https://github.com/apache/activemq-artemis/pull/4222
…alidate queue creation on reload with new test
Issue Time Tracking
-------------------
Worklog Id: (was: 809988)
Remaining Estimate: 0h
Time Spent: 10m
> properties config - have configuration refresh track properties urls
> --------------------------------------------------------------------
>
> Key: ARTEMIS-4001
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4001
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.25.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The broker supports runtime configuration updates and will apply any
> properties files that exist, however it does not track any property file
> locations for modification.
> When the broker.xml is largely read only, providing a basic template, it
> would make sense to be able to update for example_ /etc/address.properties_
> to add new queues at runtime through the normal xml refresh mechanism and
> configurationFileRefreshPeriod
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
