PLAIN, ANONYMOUS, and GSSAPI SASL mechanism. These are implemented on the broker’s security infrastructure. 6.5. AMQP and destinations If an AMQP Link is dynamic then a temporary queue will be created MQTT has been specifically designed to reduce transport overhead (and thus network traffic) and code footprint on client devices. For this reason MQTT is ideally suited to constrained devices such as connection will be terminated. In the case of MQTT 5 clients they will receive a disconnect reason code of 0x80 (i.e. "Unspecified error"). 8.10. Automatic Subscription Clean-up Sometimes MQTT 3.x clients

PLAIN, ANONYMOUS, and GSSAPI SASL mechanism. These are implemented on the broker’s security infrastructure. 6.5. AMQP and destinations If an AMQP Link is dynamic then a temporary queue will be created MQTT has been specifically designed to reduce transport overhead (and thus network traffic) and code footprint on client devices. For this reason MQTT is ideally suited to constrained devices such as connection will be terminated. In the case of MQTT 5 clients they will receive a disconnect reason code of 0x80 (i.e. "Unspecified error"). 8.10. Automatic Subscription Clean-up Sometimes MQTT clients

PLAIN, ANONYMOUS, and GSSAPI SASL mechanism. These are implemented on the broker’s security infrastructure. 6.5. AMQP and destinations If an AMQP Link is dynamic then a temporary queue will be created MQTT has been specifically designed to reduce transport overhead (and thus network traffic) and code footprint on client devices. For this reason MQTT is ideally suited to constrained devices such as connection will be terminated. In the case of MQTT 5 clients they will receive a disconnect reason code of 0x80 (i.e. "Unspecified error"). 8.10. Automatic Subscription Clean-up Sometimes MQTT clients

PLAIN, ANONYMOUS, and GSSAPI SASL mechanism. These are implemented on the broker’s security infrastructure. 6.5. AMQP and destinations If an AMQP Link is dynamic then a temporary queue will be created MQTT has been specifically designed to reduce transport overhead (and thus network traffic) and code footprint on client devices. For this reason MQTT is ideally suited to constrained devices such as connection will be terminated. In the case of MQTT 5 clients they will receive a disconnect reason code of 0x80 (i.e. "Unspecified error"). 8.10. Automatic Subscription Clean-up Sometimes MQTT clients

PLAIN, ANONYMOUS, and GSSAPI SASL mechanism. These are implemented on the broker’s security infrastructure. 6.5. AMQP and destinations If an AMQP Link is dynamic then a temporary queue will be created MQTT has been specifically designed to reduce transport overhead (and thus network traffic) and code footprint on client devices. For this reason MQTT is ideally suited to constrained devices such as connection will be terminated. In the case of MQTT 5 clients they will receive a disconnect reason code of 0x80 (i.e. "Unspecified error"). 8.10. Automatic Subscription Clean-up Sometimes MQTT 3.x clients

PLAIN, ANONYMOUS, and GSSAPI SASL mechanism. These are implemented on the broker’s security infrastructure. 6.5. AMQP and destinations If an AMQP Link is dynamic then a temporary queue will be created MQTT has been specifically designed to reduce transport overhead (and thus network traffic) and code footprint on client devices. For this reason MQTT is ideally suited to constrained devices such as connection will be terminated. In the case of MQTT 5 clients they will receive a disconnect reason code of 0x80 (i.e. "Unspecified error"). 8.10. Automatic Subscription Clean-up Sometimes MQTT 3.x clients

PLAIN, ANONYMOUS, and GSSAPI SASL mechanism. These are implemented on the broker’s security infrastructure. 6.5. AMQP and destinations If an AMQP Link is dynamic then a temporary queue will be created MQTT has been specifically designed to reduce transport overhead (and thus network traffic) and code footprint on client devices. For this reason MQTT is ideally suited to constrained devices such as connection will be terminated. In the case of MQTT 5 clients they will receive a disconnect reason code of 0x80 (i.e. "Unspecified error"). 8.10. Automatic Subscription Clean-up Sometimes MQTT 3.x clients

PLAIN, ANONYMOUS, and GSSAPI SASL mechanism. These are implemented on the broker’s security infrastructure. 6.5. AMQP and destinations If an AMQP Link is dynamic then a temporary queue will be created MQTT has been specifically designed to reduce transport overhead (and thus network traffic) and code footprint on client devices. For this reason MQTT is ideally suited to constrained devices such as connection will be terminated. In the case of MQTT 5 clients they will receive a disconnect reason code of 0x80 (i.e. "Unspecified error"). 8.10. Automatic Subscription Clean-up Sometimes MQTT 3.x clients

server-side message load-balancing. 1.0.0 Full release notes. Highlights: First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a message to only one of the ANYCAST queues

load-balancing. 1.0.0 Full release notes. Highlights: Versions 15 First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a message to only one of the ANYCAST queues