The JMX management interfaces behavior doesn't have a detailed explanation in the docs.

Would be nice to have an explanation between the differences in creating a queue through broker.xml file and Hawtio/Jolokia/JMX/amq-cli.

Today, people are using cli interfaces thorough Jolokia and Hawtio to create queues. The problem is: those configurations are only persisted at the data/bindings directory and not reflected in the broker.xml file.

This is leading to misunderstandings because:

1. One wouldn't see their queues/addresses creation in the configuration file
2. If something happens in the data/bindings directory, the queues/addresses just vanishes. In environments where automatically queue creation are disabled, clients won't be able to send nor receive messages
3. In environments where dynamically queue creation is needed, like in a CI/CD process, to have more reliability at the configuration level, have to call Jolokia endpoints plus writing in the broker.xml would be too cumbersome at the operations level (even using Ansible or other automation tool)

If one runs the following command:

$AMQ_HOME/bin/artemis data exp

The xml configuration for queues/addresses created in the bindings directory would output. So one could use it to append in the broker.xml file after properly formatting.