AMQ Broker 7.2 Release Notes
Release Notes for AMQ Broker
Chapter 1. Features
This section outlines the major features added in AMQ 7.1 and later.
- Brokers can be fully redundant, allowing a backup broker to take over connections from a primary broker in the event of a failure. Optionally, a shared volume can be configured between the primary and backup broker.
- Delivery guarantee
- Some messages that a developer sends from his application require a guarantee of delivery guaranteeing that messages get from the application sending them to the application consuming and processing them. If a network link goes down or the broker experiences a power outage while the message is in transit the message broker must resend undelivered messages once it returns online or the network connection is restored.
- Zero persistence
- Brokers can be configured to not persist any messages for scenarios in which no guarantee is required, but high performance is.
- Basic authentication
- Brokers can authenticate clients using basic username and password credentials.
- Role-based authentication
- Brokers can authenticate and authorize clients to specific queues or message addresses based on roles assigned to the client.
- SSL-encrypted connections
- Connections between clients and broker or a broker and another broker are secure and utilize SSL to encrypt the connections.
- Certificate-based authentication
- Brokers can authenticate a client connection or a connection from another broker using certificates.
- Dead connection detection
- Brokers can detect dead connections when a client has exceeded specific lifespan that can be set either on the client’s connection factory or globally on the server.
- Slow consumer detection
- Brokers can detect slow consumers and disconnect them from the server when this feature is enabled.
Refer to the ActiveMQ Artemis project for additional information: http://activemq.apache.org/artemis/index.html
Chapter 2. Enhancements
ENTMQBR-428 - Implement SASL external
AMQ Broker can now validate AMQP connections by using the identity of the connection’s SSL certificate rather than using traditional credentials such as a username and password. This benefits deployments where secure access is managed through SSL certificates.
ENTMQBR-831 - Broker should respond to changes in
AMQ Broker now retains the changes that you make to the
logging.propertiesconfiguration file without restarting the broker.
ENTMQBR-893 - Masking of password does not work with
You can now mask passwords in the JAAS configuration file
login.config. Previously, password masking was not supported for
login.config, which meant that the passwords in the file were stored in plain text.
ENTMQBR-908 - Support masked passwords in
You can now mask passwords in the
broker.xmlconfiguration file. Previously, password masking was not supported for
broker.xml, which meant that the passwords in the file were stored in plain text.
ENTMQBR-935 - Should have Ability to split
broker.xmlinto multiple files and import into
AMQ Broker now supports XML inclusions in the
broker.xmlconfiguration file, which enables you to break
broker.xmlinto separate files. For example, if you have multiple brokers that share the same set of addresses and address settings, you can define the addresses in a separate file, and then include that file in each broker’s
ENTMQBR-1056 - Add Support for DB2 v11.latest
The 7.2 version of AMQ Broker adds support for the database DB2, version 11.
ENTMQBR-1063 - Improve DB2 compatibility
AMQ Broker now supports IBM DB2 versions 10.5 and 11.1 for message storage. The following enhancements have been made:
AUTO_INCREMENTis now supported on DB2.
- You can now configure the maximum allowed time difference between the system time and DB2 time. This makes high availability more reliable, because the broker will be shut down automatically if the time difference exceeds the configured value.
- Database tables can now be created externally. Concurrent table creation checking has been improved.
ENTMQBR-1271 - Allow custom etc and data directories to be used
AMQ Broker 7.2 provides greater flexibility in storing a broker instance’s configuration files and data. Previously, a broker instance’s configuration files and data could only be stored in the
data/directories within the broker instance’s directory. Now, you can store these files in any custom directory, including locations outside of the broker instance’s directory.
ENTMQBR-1282 - Support for exclusive consumers
AMQ Broker now supports exclusive queues. An exclusive queue routes messages to a single consumer even if multiple consumers are present. In addition, the consumer that receives the messages will receive them with guaranteed message ordering so that they can be consumed in the same order in which they were produced.
ENTMQBR-1308 - Create an
ActiveMQServerPluginfor logging various broker events
Starting in AMQ Broker 7.2, logging has been improved through a new
LoggingActiveMQServerPlugin. By using this plugin, you can configure highly-informative logging about many different types of events that would otherwise only be available through debug logs.
ENTMQBR-1367 - Support SSL Certificate Revocation List
Starting in AMQ Broker 7.2, you can now specify an SSL certificate revocation list on an acceptor’s URL. If you are using SSL for client communication, this means that you can specify a list of certificates that have been revoked by the issuing certificate authority (CA) before their scheduled expiration date and should no longer be trusted.
ENTMQBR-1370 - Add
userattribute to queue in XML/JMX
When a queue is auto-created it is assigned the user name of the connecting client. This user name is now exposed as metadata on the queue and also in JMX and in the AMQ Console. You can also now configure a user on a pre-defined queue by modifying the
broker.xmlfile. This enhancement makes it possible to understand and track with whom and how queues originated.
ENTMQBR-1385 - Add support for virtual topic consumers
AMQ Broker now supports migrating existing OpenWire clients that use virtual topic subscriptions (an ActiveMQ 5.x-only feature) without requiring any changes to the client. This functionality maps the virtual topic concept to an Artemis fully qualified queue name (FQQN). By using a FQQN, you can create and access a standard Artemis topic subscriber queue.
ENTMQBR-1403 - Support referrals in LDAP login module
AMQ Broker now supports LDAP referrals. If you use LDAP referrals in your LDAP infrastructure, you can now configure the broker to use these referrals to authenticate and authorize users. You can use the broker’s JAAS LDAP login module to control how the broker handles LDAP referrals.
ENTMQBR-1918 - [AMQ7, critical-analyzer] add extra detail to output for analyzing cause of timeout
The logs for the Critical Analyzer now provide extra information about a slow-performing broker when you enable tracing on the package named
ENTMQBR-1974 - Support masked passwords in
AMQ Broker now supports masking the values of the
trust-store-passwordsettings the in
management.xmlfile. These values are used when you secure remote JMX access with SSL.
ENTMQBR-2020 - Track routed and unrouted messages to an address
Address metrics now include information about how many messages the address has received. This number is divided between routed and unrouted messages. Prior to this enhancement, it was impossible to determine if an address had received a message which was not routed, for example, in the case of a JMS topic with no subscriptions.
Chapter 3. Resolved Issues
ENTMQBR-742 - JMS Queues are not being auto-deleted for Openwire and AMQP clients
Previously, addresses and queues with
truewere not deleted when AMQ OpenWire JMS clients disconnected from them.
ENTMQBR-781 - [Error Codes] same Error Code(s) defined in different places with different reasons
In previous releases of AMQ Broker, logging error codes were not unique for all broker log messages. The duplicate and conflicting logging error codes are now corrected.
ENTMQBR-882 - Standby slave does not announce replication to master when primary slave is down
This issue occurred in past releases when multiple backup brokers, also referred to as slaves, served a single live (master) broker. In this scenario, if a primary backup broker failed, the secondary backup tried to replicate. But that operation failed, the secondary backup could not take over for the primary backup, and as a result, high-availability was lost. This issue is now resolved.
ENTMQBR-914 - [AMQ7, broker startup ] AMQ224000: Failure in initialization:
java.lang.IllegalStateException: Cannot find queue with id XXXX
In previous versions of AMQ Broker, the broker would fail to start if you had an XA transaction in the prepared state, then deleted the queue that this transaction used, and then attempted to restart the broker.
LDAPLoginModulecannot process referrals
Previously, the LDAP JAAS login module was unable to handle LDAP referrals, which caused authentication and authorization failures.
ENTMQBR-930 - Unable to login with multiple LDAP modules configured
The commit operation of the LDAP JAAS login module would always return
null, resulting in unexpected behavior when multiple instances of the module were configured in the same domain.
ENTMQBR-943 - [AMQ7, Openwire, Compression] consuming Openwire compressed
java.util.zip.DataFormatException: incorrect header check
Previously, when using the OpenWire protocol to send small, compressed ByteMessages that have JMS properties set for a queue, an exception was thrown on the consumer side when it attempted to decompress the message. See the Knowledge Base article on the Red Hat Customer Portal for more details: https://access.redhat.com/solutions/3269061.
ENTMQBR-956 - [AMQ7, AMQP, JMX, DeliveringCount] JMX operation
listDeliveringMessages()returns empty string when
In previous releases, the JMX operation
listDeliveringMessages()did not return messages that were consumed by an AMQ JMS client in a transaction. The transactional messages are now returned correctly when the JMX operation
ENTMQBR-965 - [AMQ7, openwire, exclusive consumer] AMQ6 OpenWire clients using exclusive consumer do not behave the same with an AMQ 7 broker
In AMQ 7, setting the maximum number of consumers for a queue to one did not work the same as for an exclusive consumer in AMQ 6. In AMQ 6, using an exclusive consumer means that one consumer will receive all of the messages. Any other consumers are still registered, just not consuming messages. When the current exclusive consumer leaves the queue, another consumer becomes the exclusive consumer.
Previously in AMQ 7, if you set
max-consumers = 1for a queue, when this limit is reached, the broker returned a
AMQ119200error and did not allow any new consumers to join the queue. This error no longer occurs.
ENTMQBR-966 - Unsettled AMQP messages are lost when Receiver Link is opened on remote cluster member
An issue causing message loss has been fixed in this release. Previously, if messages were sent to a broker using the AMQP address, and the address was not set on the messages, then some of the messages could be lost if they were redistributed.
ENTMQBR-967 - [AMQ 7.1.0 CR1.1] Limit non-ssl connection, handshake-timeout not configurable
Previously, the broker did not disconnect unauthenticated clients. With AMQ Broker 7.2, you can use the configuration parameter
handshake-timeoutto limit the amount of time that an unauthenticated client can remain connected.
ENTMQBR-973 - Incorrect message priority displayed in hawtio console
When viewing messages in AMQ Console, the message priority is now correct. Before, the message priority incorrectly defaulted to
ENTMQBR-1016 - [AMQ7,Hawtio]AMQ 7 hawtio console store users password in browser’s local cache after user get logout
A security issue has been fixed for AMQ Console. Before, if you logged into AMQ Console, the value of the
Passwordfield was visible from local storage in Google Chrome Developer tools.
ENTMQBR-1018 - When live-slave fails-back to master, it turns off everything down, even its console
In high-availability configurations, AMQ Console is now accessible when a slave broker returns control to the master broker. Previously, AMQ Console would become unavailable for the slave broker when it gave control back to the master broker.
ENTMQBR-1030 - Restrict directory listings of Hawtio within the web server configuration
AMQ Console no longer permits access to restricted directory listings.
ENTMQBR-1130 - Destinations undeployed when master recovers from outage
When adding destinations to a broker’s configuration file (
broker.xml) at runtime, the destinations are now preserved in the configuration file and reloaded if the broker is restarted. Previously, if you added destinations to a broker’s configuration file, the destinations would not be reloaded when the broker was restarted.
ENTMQBR-1184 - LargeMessage Produced by AMQP Protocol Can Not Be Consumed By AMQP Protocol
In previous releases, if the size of an AMQP JMS Object Message was greater than the value specified for the maximum journal record size, an exception was thrown on the broker and the consumer was not able to receive the message. This issue was caused by a problem in the AMQP large message to core message conversion process.
This issue is fixed and AMQP large messages can be sent and received as usual.
ENTMQBR-1461 - AMQP:
ObjectMessagethat was handled as a Large Message
Previously, if you were using the AMQP protocol with the Qpid JMS client, and you sent a JMS
ObjectMessagethat was also a large message (larger than the
min-large-message-size), an error would occur when the message was consumed. This error no longer occurs.
ENTMQBR-1466 - [3 HA pairs] Slave does not become live after master is killed and isolates itself
The quorum voting protocol has been corrected. Previously, in high-availability configurations consisting of three high-availability pairs with replication, this issue occasionally prevented slave brokers from taking over during a failover event. Instead, the slave broker would become isolated from the broker cluster.
ENTMQBR-1500 - Jolokia read request does not fetch all attributes
Using Jolokia, it is now possible to request all of the attributes for the broker MBean.
ENTMQBR-1548 - Implementation of AMQP interceptor is passing a null RemotingConnection reference
Previously, if you were using the interceptor API with the AMQP protocol, and you implemented the following method, the connection parameter was always null:
public boolean intercept(AMQPMessage message, RemotingConnection connection)
Now, the connection parameter is properly set.
ENTMQBR-1699 - Cannot set the message content when using
Earlier releases of AMQ Broker 7.x did not contain an option to specify the message content when using the
./artemisproducer, as the A-MQ 6.x product did. Now, the
--messageparameter is available and you can use it to specify the content of the message.
ENTMQBR-1757 - AMQ Broker throws ERROR if we update the address ANYCAST to MULTICAST or vice-versa in broker.xml
Previously, if the broker was stopped and the routing type for an existing address with queues was changed in the
broker.xmlfile, the broker would fail to restart. The relevant code for updating the configuration has been modified so that such a configuration change is possible, and even if there is an error deploying the address or queue, the broker will log the error and still start.
ENTMQBR-1878 - [AMQ7, broker shutdown, JMX connector] JVM does not exit if
connectorconfigured in management-context
In previous releases, sometimes the broker did not properly close the management context when stopping the broker. The broker would appear to be stopped, but the JVM process never fully exited. Now there are checks to ensure that the management context is always closed when stopping the broker and the JVM process exits, even when a management context
ENTMQBR-1880 - Hawtio Artemis tab disappears if we use IE
ENTMQBR-1958 - Queue preference changes to display columns not persistent through page refresh
Refreshing the AMQ Console caused changes to the default column lists of tabs to be lost. To maintain your settings, you had to refrain from refreshing the browser window. Now column list preferences are stored and reused each time you access a page and refreshing the browser does not cause settings to be lost.
ENTMQBR-1995 - Enabling TRACE-level logging in the broker leads to
ConcurrentModificationExceptionand failed operations
In previous releases, multiple threads could concurrently modify a message’s properties. This resulted in
WARNmessages in the log when TRACE-level logging was enabled. Now, concurrent access to message properties is done safely and the
WARNmessages in the log related to this issue no longer occur.
ENTMQBR-2011 - Consumer of store-forward internal queues get dropped when syncing large messages
Using temporary destinations in a clustered environment caused messages to get dropped from store and forward queues when clustering messages between brokers. As a result, the broker was not able to distribute messages across cluster nodes and needed to be restarted. Now you can safely use temporary destinations in a clustered environment.
ENTMQBR-2014 - AMQ7:
io.netty.handler.codec.DecoderException: java.lang.NullPointerExceptionin broker log
When a client connected by using an unrecognized protocol, a
NullPointerExceptionwith full stack-trace was logged. Now the AMQ Broker detects and handles unrecognized protocols more gracefully and a proper
ERRORmessage is logged.
ENTMQBR-2052 - Message load balancing off, unable to send messages to queue on other nodes instead of subscribed consumer
In releases prior to AMQ Broker 7.2.3, a recursive call would result in a
StackOverflowErrorerror message in certain conditions when message load balancing was set to
OFF.As a result, the broker would not receive messages sent from clients. In AMQ Broker 7.2.3, a verification step has been added to ensure that a recursive call will not become infinite. Now, brokers receive any message sent by a client even when message load balancing is set to
ENTMQBR-2055 - [Hawtio] console display blank ClientID for the core client
When using releases prior to AMQ Broker 7.2.3 with AMQ Console, the field named Client ID was not populated when viewing a AMQ Core Protocol JMS Client connection for a producer or consumer. Now, the value of Client ID is visible in AMQ Console for AMQ Core Protocol JMS Client connections.
ENTMQBR-2086 - [AMQ 7, JMS Selectors] JMS Selectors broken in some cases
With each supported protocol, fields such as
AMQGroupIDwere not properly parsed by the filter parser. As a result, you could not create a filter using any query that used those field names. To correct this issue, wrappers to parse these pseudo-fields were implemented and now filters correctly parse the input.
For additional details about issues resolved in maintenance releases, see the following articles:
Chapter 4. Known Issues
ENTMQBR-17 - AMQ222117: Unable to start cluster connection
A broker cluster may fail to initialize properly in environments that support IPv6. The failure is due to a
SocketExceptionthat is indicated by the log message
Can’t assign requested address. To work around this issue, set the
java.net.preferIPv4Stacksystem property to
ENTMQBR-463 - Attributes in clustering settings have order restrictions. Would be nice to either have better error message or simply ignore the order
Currently the sequence of the elements in the cluster connection configuration has to be in a specific order. The workaround is to adhere to the order in the configuration schema.
ENTMQBR-520 - Receiving from address named the same as a queue bound to another address should not be allowed
A queue with the same name as an address must only be assigned to address. Creating a queue with the same name as an existing address, but bound to an address with a different name, is an invalid configuration. Doing so can result in incorrect messages being routed to the queue.
ENTMQBR-569 - Conversion of IDs from OpenWire to AMQP results in sending IDs as binary
When communicating cross-protocol from an A-MQ 6 OpenWire client to an AMQP client, additional information is encoded in the application message properties. This is benign information used internally by the broker and can be ignored.
ENTMQBR-599 - Define truststore and keystore by Artemis cli
Creating a broker instance by using the
--ssl-trust-passwordparameters does not work. To work around this issue, set the corresponding properties manually in
bootstrap.xmlafter creating the broker.
ENTMQBR-617 - Cert based authentication does not work with AMQP and OpenWire clients
Authentication based on SSL certificates is not supported for AMQP and OpenWire clients.
ENTMQBR-636 - Journal breaks, causing
JavaNullPointerException, under perf load (mpt)
To prevent IO-related issues from occurring when the broker is managing heavy loads, verify that the JVM is allocated with enough memory and heap space. See the section titled "Tuning the VM" in the Performance Tuning chapter of the ActiveMQ Artemis documentation.
ENTMQBR-648 - JMS Openwire client is unable to send messages to queue with defined
Using an A-MQ 6 JMS client to send messages to an address that has a queue with
truefails if the queue has no consumers. It is recommended that you do not set the
purgeOnNoConsumeroption when using A-MQ 6 JMS clients.
ENTMQBR-652 - List of known
This version of
amq-jon-pluginhas known issues with the MBeans for broker and queue.
Issues with the broker MBean:
Closing a connection throws
Adding address settings throws
getConnectorServices()operation cannot be found
listConsumersAsJSON()operation cannot be found
getDivertNames()operation cannot be found
Listing network topology throws
- Remove address settings has wrong parameter name
Issues with the queue MBean:
expireMessage()throws argument type mismatch exception
IllegalArgumentExceptionwith error message argument type mismatch
IllegalArgumentExceptionwith error message argument type mismatch
removeMessages()throws exception with error Can’t find operation removeMessage with 2 arguments
retryMessage()throws argument type mismatch
- Closing a connection throws
ENTMQBR-655 - [AMQP] Unable to send message when
The configuration option
populate-validated-useris not supported for messages produced using the AMQP protocol.
ENTMQBR-897 - Openwire client/protocol issues with special characters in destination name
Currently AMQ OpenWire JMS clients cannot access queues and addresses that include the following characters in their name: comma (','), hash ('#'), greater than ('>'), and whitespace.
ENTMQBR-944 - [A-MQ7, Hawtio, RBAC] User gets no feedback if operation access was denied by RBAC
The console can indicate that an operation attempted by an unauthorized user was successful when it was not.
ENTMQBR-945 - Non-persistent messages lost in non-failure scenarios when authorization fails, because delivery mode defaults to asynchronous
Clients may not notice the loss of non-persistent messages. Message loss is often associated with an obvious failure, such as the broker stopping or the storage provider disconnecting. However, the asynchronous behavior of the default delivery mode can lead to the loss of non-persistent messages in other situations too, such as failing authorization or trying to use a queue that is not configured.
Client connection failedmessage in broker log with OpenWire client
Currently, when an OpenWire client (ActiveMQ) disconnects cleanly, the broker shows a warning message similar to the following:
Client connection failed, clearing up resources for session ID:localhost-45795-1527065581471-5:1:1
This warning can be safely ignored.
ENTMQBR-1848 - "javax.jms.JMSException: Incorrect Routing Type for queue, expecting: ANYCAST" occurs when qpid-jms client consumes a message from a multicast queue as
javax.jms.Queueobject with FQQN
Currently, sending a message by using the Qpid JMS client to a multicast queue by using FQQN (fully qualified queue name) to an address that has multiple queues configured generates an error message on the client, and the message cannot be sent. To work around this issue, modify the broker configuration to resolve the error and unblock the client.
ENTMQBR-2068 - some messages received but not delivered during HA fail-over, fail-back scenario
Currently, if a broker fails over to its slave while an OpenWire client is sending messages, messages being delivered to the broker when failover occurs could be lost. To work around this issue, ensure that the broker persists the messages before acknowledging them.