Chapter 2. Enhancements

ENTMQBR-283 - AMQP - Send & Receive very large messages

Previously, clients using the AMQP protocol could not receive messages larger than the value set for the journal-buffer-size element in the broker.xml configuration file. This limit is removed in 7.1. However, because the messages are stored in memory, their size is still limited by the amount of memory available.

ENTMQBR-357 - Implement a Kerberos Authentication Mechanism between clients and the broker

Previously, the broker could not be used for authenticating clients that used Kerberos credentials. The 7.1 version of AMQ Broker allows Kerberos to be used for authentication between clients and brokers.

ENTMQBR-427 - limit non-ssl connection hangs up exceeding client(s)

Previously, unauthenticated clients were not disconnected by the broker. The 7.1 version of AMQ Broker includes the configuration parameter max-negotiate-time, which limits the amount of time an unauthenticated client can remain connected.

ENTMQBR-432 - create more granular control of management authorisation

Previously, securing access to the JMX management API was limited to granting users either full access or none at all. The 7.1 version of AMQ Broker allows for more granularity when granting user access to JMX objects and methods. The security section of the configuration now includes whitelist, default-access, and role-access sub-elements. See the section "Setting Role Based Access Control" in the product documentation titled "Using AMQ Broker".

ENTMQBR-483 - Implement large message support for OpenWire

Previously, clients using the OpenWire protocol could not receive messages that were larger than the value set for the journal-buffer-size element in the broker.xml configuration file. This limit is removed in 7.1. However, because messages are stored in memory, their size is still limited by the amount of memory available.

ENTMQBR-773 - Provide option to disable/hide advisories created from openwire clients

The broker automatically creates one or more advisory queues were when an OpenWire client connected to the broker. Creating a large number of advisory queues can affect system resources. The 7.1 version of AMQ Broker includes two new configuration parameters. The first, supportAdvisory, controls the use of advisory messages, and suppressInternalManagementObjects controls their display in the console.

ENTMQBR-789 - Add support for Ldap role mapping of kerberos authenticated users

The 7.1 version of AMQ Broker can query an LDAP directory to discover the roles assigned to a Kerberos-authenticated user. Discovered roles can be mapped to roles created in the broker configuration. See the "Security" chapter of the product documentation titled Using AMQ Broker for more information.

ENTMQBR-790 - Add support for authentication to ldap via kerberos for ldapLoginModule

Previously, the broker could not connect to an LDAP provider by using Kerberos credentials. In the 7.1 version of AMQ Broker, you can enable the broker to use Kerberos by adding configuration to the login.config configuration file. See the "Security" chapter of the product documentation titled Using AMQ Broker for more information.

ENTMQBR-811 - Enable the ability to configure maxFramePayloadSize for STOMP over WebSocket

Previously, when using STOMP client and WebSockets, you could not send messages with a payload greater than 65 kilobytes in size, which was the default limit. Using 7.1 version of AMQ Broker, you can limit the size of a message directly by adding the maxWebSocketFrameSize parameter to the connection string URI and providing the appropriate value in kilobytes.

ENTMQBR-827 - Lock down jolokia by default in a-mq

Previously, the AMQ Console was accessible from any host. In 7.1, the Console can be accessed only from localhost by default. You can change the access rules using the new configuration file management-access.xml. See the product documentation titled "Using AMQ Console" for more information about configuration options.

ENTMQBR-898 - [AMQ7, Plugin support] Artemis Plugin Support

With the 7.1 version of AMQ Broker, you can develop plug-ins that intercept events in the broker for custom handling. Events that a plug-in could intercept include security-related method calls and the creation of queues and addresses.