metrics • Support for resetting queue properties by unsetting them in broker.xml • Undeploy diverts by removing them from broker.xml • Add addressMemoryUsagePercentage and addressSize as metrics ## Upgrading it's worth mentioning here anyway. Prior to 2.14.0 if you configured a parameter on a queue in broker.xml (e.g. max-consumers) and then later removed that setting the configured value you set would remain remain. This has changed in 2.14.0 via ARTEMIS-2797. Any value that is not explicitly set in broker.xml will be set back to either the static default or the dynamic default configured in the address-settings

metrics • Support for resetting queue properties by unsetting them in broker.xml • Undeploy diverts by removing them from broker.xml • Add addressMemoryUsagePercentage and addressSize as metrics ## Upgrading Upgrading from older versions Make sure the existing queues have their parameters set according to the broker.xml values before upgrading. #### 2.13. 0 Full release notes. Highlights: • Management methods acceptor to more easily identify the acceptor which has the problem. - The CLI will now read the broker.xml to find the default connector URL for commands which require it (e.g. consumer, producer, etc.)

metrics • Support for resetting queue properties by unsetting them in broker.xml • Undeploy diverts by removing them from broker.xml • Add addressMemoryUsagePercentage and addressSize as metrics ## Upgrading it's worth mentioning here anyway. Prior to 2.14.0 if you configured a parameter on a queue in broker.xml (e.g. max-consumers) and then later removed that setting the configured value you set would remain remain. This has changed in 2.14.0 via ARTEMIS-2797. Any value that is not explicitly set in broker.xml will be set back to either the static default or the dynamic default configured in the address-settings

metrics • Support for resetting queue properties by unsetting them in broker.xml • Undeploy diverts by removing them from broker.xml • Add addressMemoryUsagePercentage and addressSize as metrics ## Upgrading it's worth mentioning here anyway. Prior to 2.14.0 if you configured a parameter on a queue in broker.xml (e.g. max-consumers) and then later removed that setting the configured value you set would remain remain. This has changed in 2.14.0 via ARTEMIS-2797. Any value that is not explicitly set in broker.xml will be set back to either the static default or the dynamic default configured in the address-settings

broker to refresh various configuration files and scripts for an existing broker instance. The broker.xml and data are left in place as-is. You should back up your existing broker instance before running properties file. Note also that brokers configuration-file-refresh-period broker.xml setting no longer covers logging configuration refresh. Log4J 2 has its own configuration reload metrics • Support for resetting queue properties by unsetting them in broker.xml • Undeploy diverts by removing them from broker.xml • Add addressMemoryUsagePercentage and addressSize as metrics ## Upgrading

metrics • Support for resetting queue properties by unsetting them in broker.xml • Undeploy diverts by removing them from broker.xml • Add addressMemoryUsagePercentage and addressSize as metrics ## Upgrading it's worth mentioning here anyway. Prior to 2.14.0 if you configured a parameter on a queue in broker.xml (e.g. max-consumers) and then later removed that setting the configured value you set would remain remain. This has changed in 2.14.0 via ARTEMIS-2797. Any value that is not explicitly set in broker.xml will be set back to either the static default or the dynamic default configured in the address-settings

metrics • Support for resetting queue properties by unsetting them in broker.xml • Undeploy diverts by removing them from broker.xml • Add addressMemoryUsagePercentage and addressSize as metrics ## Upgrading it's worth mentioning here anyway. Prior to 2.14.0 if you configured a parameter on a queue in broker.xml (e.g. max-consumers) and then later removed that setting the configured value you set would remain remain. This has changed in 2.14.0 via ARTEMIS-2797. Any value that is not explicitly set in broker.xml will be set back to either the static default or the dynamic default configured in the address-settings

the Jolokia JMX-HTTP bridge. - Due to ARTEMIS-4212 the broker will reject address definitions in broker.xml which don't specify a routing type, e.g.:

Such configurations broker to refresh various configuration files and scripts for an existing broker instance. The broker.xml and data are left in place as-is. You should back up your existing broker instance before running changes for the new log4j2.properties file. Note also that brokers configuration-file-refresh-period broker.xml setting no longer covers logging configuration refresh. Log4J 2 has its own configuration reload

broker to refresh various configuration files and scripts for an existing broker instance. The broker.xml and data are left in place as-is. You should back up your existing broker instance before running properties file. Note also that brokers configuration-file-refresh-period broker.xml setting no longer covers logging configuration refresh. Log4J 2 has its own configuration reload metrics • Support for resetting queue properties by unsetting them in broker.xml • Undeploy diverts by removing them from broker.xml • Add addressMemoryUsagePercentage and addressSize as metrics ## Upgrading

the Jolokia JMX-HTTP bridge. - Due to ARTEMIS-4212 the broker will reject address definitions in broker.xml which don't specify a routing type, e.g.:

Such configurations broker to refresh various configuration files and scripts for an existing broker instance. The broker.xml and data are left in place as-is. You should back up your existing broker instance before running changes for the new log4j2.properties file. Note also that brokers configuration-file-refresh-period broker.xml setting no longer covers logging configuration refresh. Log4J 2 has its own configuration reload