Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

NO-JIRA update version doc for release

This commit is contained in:
Justin Bertram 2024-12-12 22:59:41 -06:00
parent 7eaea5a7a6
commit 9f2a24a927
No known key found for this signature in database
GPG Key ID: F41830B875BB8633
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/user-manual/versions.adoc
View File

@ -19,6 +19,12 @@ https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&versio
=== Highlights
* *Java 17 is now required.*
* 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 xref:configuration-index.adoc#broker-properties[properties].
* Failure conditions for xref:using-cli.adoc#command-line-interface[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.
=== Upgrading from 2.38.0
@ -29,6 +35,7 @@ Security is critical for us and most of our users so we therefore need to upgrad
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.
* Due to https://issues.apache.org/jira/browse/ARTEMIS-5153[ARTEMIS-5153] the queues related to AMQP federation events and and controls are now marked as _internal_.
== 2.38.0