I'm pleased to announce the release of ActiveMQ Artemis 2.39.0. * Downloads: https://activemq.apache.org/components/artemis/download/
* Complete list of updates: https://activemq.apache.org/components/artemis/download/release-notes-2.39.0 I would like to highlight these improvements: - Java 17 is now required. support for Java 11 has been dropped. The main reason for this change is that the version of Jetty we were embedding in previous versions (i.e. 10) will officially reach its end-of-life on January 1, 2025 [1] and will therefore no longer be receiving any fixes - including security fixes. Security is critical for us and most of our users so we therefore need to upgrade to Jetty 12 - the only version of Jetty now supported. Jetty 12 requires Java 17 so we must also move to Java 17 and drop support for Java 11. Please note that after upgrading the broker to Java 17 it will be backwards compatible with all previous clients. - AMQP federation and broker connections have new management controls. - The Core client (including the Core JMS client) supports a configurable timeout for onMessage invocations when closing/stopping a connection. - Datasource configuration is now available when configuring the broker via properties. - Failure conditions for CLI commands (e.g. artemis check) now specifically return an exit code of 1 which means they can be more reliably incorporated into other scripts, etc. - The binary distribution is almost 8MB smaller than 2.38.0 due to reduced dependencies. - Lots of fixes for various flaky tests. This reduces spurious test failures improving the experience for developers building the broker and running the test-suite. As usual it contains a handful of bug fixes and other improvements. Many thanks to all those who contributed to this release! Justin
