versions Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: 1. etc/bootstrap.xml 2. etc/management.xml In both files change the XML namespace from activemq.org to activemq.apache.org , e.g. in bootsrap.xml use: And in management.xml use: 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

versions 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: i. etc/bootstrap.xml ii. etc/management.xml In both files change the XML namespace from activemq.org to activemq.apache.org , e.g. in bootsrap.xml use: And in management.xml use: 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 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 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 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 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

Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: i. etc/bootstrap.xml ii. etc/management.xml Versions 10 In both files change the XML namespace activemq.org to activemq.apache.org , e.g. in bootsrap.xml use: And in management.xml use: 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

versions 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: i. etc/bootstrap.xml ii. etc/management.xml In both files change the XML namespace from activemq.org to activemq.apache.org , e.g. in bootsrap.xml use: And in management.xml use: 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

addresses. Support downstream federated queues and addresses. Make security manager configurable via XML. Support pluggable SSL TrustManagerFactory. Add plugin support for federated queues/addresses. Support Windows Locate this part of JAVA_ARGS in etc/artemis.profile.cmd respectively bin/artemis-service.xml : %ARTEMIS_HOME%\lib\wildfly-common-1.5.1.Final.jar Versions 8 This needs to be replaced with this: Windows Locate this part of JAVA_ARGS in etc/artemis.profile.cmd respectively bin/artemis-service.xml : -Xbootclasspath/a:%ARTEMIS_HOME%\lib\jboss-logmanager-2.1.10.Final.jar This needs to be replaced

10 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 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