Improved JDBC connection management New web console based on Hawtio 2 Performance optimizations (i.e. caching) for authentication and authorization Versions 11 Support for admin objects in the JCA integrity issues related to concurrent modification. From a user's perspective two main things changed: i. User management is no longer possible using the artemis user commands when the broker is offline main ways for users to track rates of message production and consumption (in recommended order): i. Use a metrics plugin. This is the most feature-rich and flexible way to track broker metrics, although

Improved JDBC connection management New web console based on Hawtio 2 Performance optimizations (i.e. caching) for authentication and authorization Support for admin objects in the JCA resource adapter related to concurrent modification. From a user's perspective two main things changed: Versions 11 i. User management is no longer possible using the artemis user commands when the broker is offline main ways for users to track rates of message production and consumption (in recommended order): i. Use a metrics plugin. This is the most feature-rich and flexible way to track broker metrics, although

Improved JDBC connection management New web console based on Hawtio 2 Performance optimizations (i.e. caching) for authentication and authorization Support for admin objects in the JCA resource adapter related to concurrent modification. From a user's perspective two main things changed: Versions 11 i. User management is no longer possible using the artemis user commands when the broker is offline main ways for users to track rates of message production and consumption (in recommended order): i. Use a metrics plugin. This is the most feature-rich and flexible way to track broker metrics, although

JDBC connection management Versions 9 New web console based on Hawtio 2 Performance optimizations (i.e. caching) for authentication and authorization Support for admin objects in the JCA resource adapter xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL Support for additional messaging use-cases. Eliminates confusing JMS-specific queue naming conventions (i.e. "jms.queue." & "jms.topic." prefixes). Pure encoding of messages so protocols like AMQP don't need

xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL Support for additional messaging use-cases. Eliminates confusing JMS-specific queue naming conventions (i.e. "jms.queue." & "jms.topic." prefixes). Pure encoding of messages so protocols like AMQP don't need queue and publish-subscribe messaging patterns. JMS is a lowest common denominator specification - i.e. it was created to encapsulate common functionality of the already existing messaging systems that

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 Improved JDBC connection management New web console based on Hawtio 2 Performance optimizations (i.e. caching) for authentication and authorization Support for admin objects in the JCA resource adapter integrity issues related to concurrent modification. From a user's perspective two main things changed: i. User management is no longer possible using the artemis user commands when the broker is offline

Improved JDBC connection management New web console based on Hawtio 2 Performance optimizations (i.e. caching) for authentication and authorization Support for admin objects in the JCA resource adapter integrity issues related to concurrent modification. From a user's perspective two main things changed: i. User management is no longer possible using the artemis user commands when the broker is offline main ways for users to track rates of message production and consumption (in recommended order): i. Use a metrics plugin. This is the most feature-rich and flexible way to track broker metrics, although

xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL Support for additional messaging use-cases. Eliminates confusing JMS-specific queue naming conventions (i.e. "jms.queue." & "jms.topic." prefixes). Pure encoding of messages so protocols like AMQP don't need queue and publish-subscribe messaging patterns. JMS is a lowest common denominator specification - i.e. it was created to encapsulate common functionality of the already existing messaging systems that

Improved JDBC connection management New web console based on Hawtio 2 Performance optimizations (i.e. caching) for authentication and authorization Support for admin objects in the JCA resource adapter xm and login.config Configurable broker plugin implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL Support for additional messaging use-cases. Eliminates confusing JMS-specific queue naming conventions (i.e. "jms.queue." & "jms.topic." prefixes). Pure encoding of messages so protocols like AMQP don't need

submitted by the client application. This will impact use-cases like the following: Versions 9 i. When login.config is configured with the GuestLoginModule which causes some users to be assigned subject DN from their SSL certificate. In these kinds of situations the broker will use this assigned (i.e. validated) username for any queues created with the connection. In the past the queue's username 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