Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session 3.x subscriber using CleanSession=1 is now non-durable rather than durable. This may impact security-settings for MQTT clients which previously only had createDurableQueue for their role. They cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle attacks). Enabling it by default aligns core client behavior

Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session 3.x subscriber using CleanSession=1 is now non- durable rather than durable. This may impact security-settings for MQTT clients which previously only had createDurableQueue for their role. They cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in- the-middle attacks). Enabling it by default aligns core client behavior

Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Failover Diverting 3.x subscriber using CleanSession=1 is now non-durable rather than durable. This may impact security-settings for MQTT clients which previously only had createDurableQueue for their role. They cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle attacks). Enabling it by default aligns core client behavior

Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Failover Diverting 3.x subscriber using CleanSession=1 is now non-durable rather than durable. This may impact security-settings for MQTT clients which previously only had createDurableQueue for their role. They cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle attacks). Enabling it by default aligns core client behavior

Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session and ARTEMIS-3010 2.15.0 Full release notes. Highlights: Ability to use FQQN syntax for both security-settings and JNDI lookup Support pausing dispatch during group rebalance (to avoid potential out-of- Per-acceptor security domains Command-line check tool for checking the health of a broker Support disabling metrics per address via the enable-metrics address setting Improvements to the audit logging

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6.4. AMQP and security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 29.2. Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 43.2. Role based security for addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 43.3. Security Setting Plugin . . . . . .

Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line check tool for checking the health of a broker Support disabling metrics setting Versions 9 Improvements to the audit logging Speed optimizations for the HierarchicalObjectRepository , an internal object used to store address and security settings Upgrading from older versions

Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle attacks). Enabling it by default aligns core client behavior recommended option with regard to security. Update any connector using sslEnabled=true to also use verifyHost=false . Using this option means that you won't get the extra security of hostname verification

Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session 3.x subscriber using CleanSession=1 is now non-durable rather than durable. This may impact security-settings for MQTT clients which previously only had createDurableQueue for their role. They cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle attacks). Enabling it by default aligns core client behavior

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6.4. AMQP and security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 28.2. Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 42.2. Role based security for addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 42.3. Security Setting Plugin . . . . . .