Red Hat SummitRed Hat AMQ 6
As of February 2025, Red Hat is no longer supporting Red Hat AMQ 6. If you are using AMQ 6, please upgrade: Migrating to AMQ 7.Este contenido no está disponible en el idioma seleccionado.
1.3. New Features
MQTT transport
Red Hat JBoss A-MQ now supports the MQTT (MQ Telemetry Transport) transport. There are three variations of the MQTT transport: plain MQTT (
mqtt: URL), MQTT+NIO (mqtt+nio: URL), and MQTT+NIO+SSL (mqtt+nio+ssl: URL).
Note
You cannot use the MQTT transport with the JMS client API, because the provided implementation of the JMS client API supports only the Openwire protocol. You must use a dedicated MQTT client to connect to the broker over the MQTT transport.
Stomp 1.2
Red Hat JBoss A-MQ now supports Stomp version 1.2.
Note
You cannot use the Stomp transport with the JMS client API, because the provided implementation of the JMS client API supports only the Openwire protocol. You must use a dedicated Stomp client to connect to the broker over the Stomp transport.
MS SQL JDBC driver 4.0
Red Hat JBoss A-MQ now supports using MS SQL JDBC driver 4.0 with the JDBC persistence adapter.
JMS selector expressions
In order to be compliant with the JMS specification,
String property values are no longer converted automatically into numeric values in ActiveMQ 5.8.
For example, if a message has an
age property equal to the string value, 21, the selector, age > 18, will not match the property value in ActiveMQ version 5.8. If you would prefer the property to match the selector in this case (by converting the string to a numeric value), you can use the following selector instead: convert_string_expressions:age > 18.
Published address policy
It is now possible to specify whether a broker should advertise its endpoint address using a hostname, numeric IP address, or a fully-qualified domain name (FQDN). You can specify this policy by setting the
publishedAddressPolicy attribute on the broker's transportConnector element.
