0 is available here for *nix or here for Windows. 2.26.0 Full release notes Highlights: Bug fixes and improvements Upgrading from older versions 1. We removed the *-all clients from ./lib/client use these libraries they can be found at Maven Central, please refer to the client class path documentation for more information. 2. We removed ActiveMQ-Artemis rest as part of 2.26.0. If you still require its latest version at Maven central. You can still follow the steps on Rest from any previous documentation, however you should stop using the module as it will not be maintained any more. 3. We removed

filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. 7.7. STOMP and JMS interoperability 7.7.1. Sending and consuming STOMP message from JMS or JavaScript library to ease client-side development is available from GitHub (please see its documentation for a complete description). The payload length of Web Socket frames can vary between client tcp://remote-host:5445?ssl-enabled=true. All the properties available for the tcp scheme are described in the documentation regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then

filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. 7.7. STOMP and JMS interoperability 7.7.1. Sending and consuming STOMP message from JMS or JavaScript library to ease client-side development is available from GitHub (please see its documentation for a complete description). The payload length of Web Socket frames can vary between client tcp://remote-host:5445?ssl-enabled=true. All the properties available for the tcp scheme are described in the documentation regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then

filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. 7.7. STOMP and JMS interoperability 7.7.1. Sending and consuming STOMP message from JMS or JavaScript library to ease client-side development is available from GitHub (please see its documentation for a complete description). The payload length of Web Socket frames can vary between client tcp://remote-host:5445?ssl-enabled=true. All the properties available for the tcp scheme are described in the documentation regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then

filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. 7.7. STOMP and JMS interoperability 7.7.1. Sending and consuming STOMP message from JMS or JavaScript library to ease client-side development is available from GitHub (please see its documentation for a complete description). The payload length of Web Socket frames can vary between client tcp://remote-host:5445?ssl-enabled=true. All the properties available for the tcp scheme are described in the documentation regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then

filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. 7.7. STOMP and JMS interoperability 7.7.1. Sending and consuming STOMP message from JMS or JavaScript library to ease client-side development is available from GitHub (please see its documentation for a complete description). The payload length of Web Socket frames can vary between client tcp://remote-host:5445?ssl-enabled=true. All the properties available for the tcp scheme are described in the documentation regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then

filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. 7.8. STOMP and JMS interoperability 7.8.1. Sending and consuming STOMP message from JMS or JavaScript library to ease client-side development is available from GitHub (please see its documentation for a complete description). The payload length of Web Socket frames can vary between client tcp://remote-host:5445?ssl-enabled=true. All the properties available for the tcp scheme are described in the documentation regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then

filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. 7.8. STOMP and JMS interoperability 7.8.1. Sending and consuming STOMP message from JMS or JavaScript library to ease client-side development is available from GitHub (please see its documentation for a complete description). The payload length of Web Socket frames can vary between client tcp://remote-host:5445?ssl-enabled=true. All the properties available for the tcp scheme are described in the documentation regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then

filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. 7.8. STOMP and JMS interoperability 7.8.1. Sending and consuming STOMP message from JMS or JavaScript library to ease client-side development is available from GitHub (please see its documentation for a complete description). The payload length of Web Socket frames can vary between client tcp://remote-host:5445?ssl-enabled=true. All the properties available for the tcp scheme are described in the documentation regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then

the details. 2.29.0 Full release notes Highlights: This version underwent extensive testing and fixes regarding Large Messages, with a few JIRAs dedicated to this topic. Look on the release notes for restored and properly deprecated for future removal. 2.28.0 Full release notes Highlights: Bug Fixes and improvements as usual ARTEMIS-4136 Mirror sync replication Mirror now has an option to set sync=true messages to the new subscription queue administratively. 2.27.1 Full release notes Highlights: Bug Fixes AMQP Large Message over Bridges were broken Rollback of massive transactions would take a long time