e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files. Enhanced message count and size metrics 1.x clients needs to have anycastPrefix=jms.queue.;multicastPrefix=jms.topic. in the acceptor url. This prefix used to be configured automatically behind the scenes when the broker detected these remove the Jolokia war file from the web element in /etc/bootstrap.xml : url="jolokia" war="jolokia.war"/> This is no longer required as the Jolokia REST interface is now integrated

Subject Alternative Name values of the broker's SSL certificate to match the hostname in the client's URL. This impacts all core-based clients including core JMS clients and core connections between cluster following: Update your SSL certificates to use a hostname which matches the hostname in the client's URL. This is the recommended option with regard to security. Update any connector using sslEnabled=true 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.) 2.11.0 Versions 15 Full release

Subject Alternative Name values of the broker's SSL certificate to match the hostname in the client's URL. This impacts all core-based clients including core JMS clients and core connections between cluster following: Update your SSL certificates to use a hostname which matches the hostname in the client's URL. This is the recommended option with regard to security. Update any connector using sslEnabled=true 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.) 2.11.0 Full release notes. Highlights:

Subject Alternative Name values of the broker's SSL certificate to match the hostname in the client's URL. This impacts all core-based clients including core JMS clients and core connections between cluster following: Update your SSL certificates to use a hostname which matches the hostname in the client's URL. This is the recommended option with regard to security. Update any connector using sslEnabled=true 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.) 2.11.0 Versions 16 Full release

e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files. Enhanced message count and size metrics 1.x clients needs to have anycastPrefix=jms.queue.;multicastPrefix=jms.topic. in the acceptor url. This prefix used to be configured automatically behind the scenes when the broker detected these remove the Jolokia war file from the web element in /etc/bootstrap.xml : url="jolokia" war="jolokia.war"/> This is no longer required as the Jolokia REST interface is now integrated

LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files. Enhanced message count and size metrics 1.x clients needs to have anycastPrefix=jms.queue.;multicastPrefix=jms.topic. in the acceptor url. This prefix used to be configured automatically behind the scenes when the broker detected these remove the Jolokia war file from the web element in /etc/bootstrap.xml : url="jolokia" war="jolokia.war"/> This is no longer required as the Jolokia REST interface is now integrated

multicastPrefix parameters within the URL of an acceptor. Configuring an Anycast Prefix Address Model 31 In /etc/broker.xml, add the anycastPrefix to the URL of the desired acceptor. In the example Configuring a Multicast Prefix In /etc/broker.xml, add the anycastPrefix to the URL of the desired acceptor. In the example below, the acceptor is configured to use multicast:// for invmConnectionFactory1=vm://1 connectionFactory.invmConnectionFactory2=vm://2 Here is a list of all the supported URL schemes: vm tcp udp jgroups Most clients won't be connecting to an embedded broker. Clients

LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files. Enhanced message count and size metrics 1.x clients needs to have anycastPrefix=jms.queue.;multicastPrefix=jms.topic. in the acceptor url. This prefix used to be configured automatically behind the scenes when the broker detected these remove the Jolokia war file from the web element in /etc/bootstrap.xml : url="jolokia" war="jolokia.war"/> This is no longer required as the Jolokia REST interface is now integrated

e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files. Enhanced message count and size metrics 1.x clients needs to have anycastPrefix=jms.queue.;multicastPrefix=jms.topic. in the acceptor url. This prefix used to be configured automatically behind the scenes when the broker detected these remove the Jolokia war file from the web element in /etc/bootstrap.xml : url="jolokia" war="jolokia.war"/> This is no longer required as the Jolokia REST interface is now integrated

multicastPrefix parameters within the URL of an acceptor. Configuring an Anycast Prefix Address Model 45 In /etc/broker.xml, add the anycastPrefix to the URL of the desired acceptor. In the example Configuring a Multicast Prefix In /etc/broker.xml, add the anycastPrefix to the URL of the desired acceptor. In the example below, the acceptor is configured to use multicast:// for invmConnectionFactory1=vm://1 connectionFactory.invmConnectionFactory2=vm://2 Here is a list of all the supported URL schemes: vm tcp udp jgroups Most clients won't be connecting to an embedded broker. Clients