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

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 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 cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- Versions 10 middle attacks). Enabling it by default aligns core 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 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