change on disk • Performance improvements on mirroring and paging • Logging metrics to mitigate the risk of missing WARN or ERROR messages in the log. • Much improved documentation on network isolation This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with

change on disk • Performance improvements on mirroring and paging • Logging metrics to mitigate the risk of missing WARN or ERROR messages in the log. • Much improved documentation on network isolation This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with

change on disk • Performance improvements on mirroring and paging • Logging metrics to mitigate the risk of missing WARN or ERROR messages in the log. • Much improved documentation on network isolation This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with

change on disk • Performance improvements on mirroring and paging • Logging metrics to mitigate the risk of missing WARN or ERROR messages in the log. • Much improved documentation on network isolation This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with

This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with OFF , so that addresses, queues and diverts aren't removed upon configuration reload, reducing the risk of losing messages. Addresses, queues and diverts no longer present in the configuration file can

This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with OFF , so that addresses, queues and diverts aren't removed upon configuration reload, reducing the risk of losing messages. Addresses, queues and diverts no longer present in the configuration file can

This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with cluster may change relatively frequently. When scaling up a cluster (i.e. adding nodes) there is no risk of message loss, but when scaling down a cluster (i.e. removing nodes) the messages on those nodes

This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with cluster may change relatively frequently. When scaling up a cluster (i.e. adding nodes) there is no risk of message loss, but when scaling down a cluster (i.e. removing nodes) the messages on those nodes

This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with cluster may change relatively frequently. When scaling up a cluster (i.e. adding nodes) there is no risk of message loss, but when scaling down a cluster (i.e. removing nodes) the messages on those nodes

This is a precautionary measure to ensure no unanticipated MBean deployed with the broker poses a risk. However, this will also impact JVM-specific and platform MBeans as well (e.g. which allow manual 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 with cluster may change relatively frequently. When scaling up a cluster (i.e. adding nodes) there is no risk of message loss, but when scaling down a cluster (i.e. removing nodes) the messages on those nodes