If addresses and related artefacts are added to broker.xml, these take effect in the broker immediately, and are visible in the broker console. However, removing addresses (etc) has no effect. This behaviour seems to be by design, because we don't want a situation where editing broker.xml with a text editor could end up deleting data (see ENTMQBR-693).

However, where broker.xml is created using instrumentation, inconsistencies between the broker.xml and the internal state of the broker could be problematic. So it would be useful to have the option for the broker to respond to configuration files changes that potentially delete data, if the administrator specifically requests.