You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@artemis.apache.org by Domenico Francesco Bruscino <br...@apache.org> on 2026/08/27 08:29:49 UTC
[ANNOUNCE] Apache Artemis 2.56.0 Released
I'm pleased to announce the release of Apache Artemis 2.56.0.
* Downloads:
https://artemis.apache.org/components/artemis/download/
* Complete list of updates:
https://artemis.apache.org/components/artemis/download/release-notes-2.56.0
I would like to highlight these improvements:
- The lock coordinators now support a new `auto-start` attribute to
control whether a coordinator begins polling for the distributed lock
on broker activation, plus new `startLockCoordinator` /
`stopLockCoordinator` management operations and matching `lock start`
/ `lock stop` CLI commands.
- A lock coordinator that cannot reach its distributed lock store
(e.g. ZooKeeper is unreachable) no longer hangs broker shutdown
indefinitely.
- The AMQP protocol module has been updated to proton-j 0.35.0 with a
new `maxTransfersPerDelivery` configuration option.
- The journal file lock health-check behavior is now configurable via
the new `journal-lock-monitor-timeout` and
`journal-lock-monitor-max-retries` parameters in `broker.xml`.
- MQTT QoS 1 and QoS 2 message delivery has been redesigned for
resiliency across broker restarts and client reconnects.
As usual it contains a handful of bug fixes and other improvements.
Many thanks to all those who contributed to this release!
Domenico
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@artemis.apache.org
For additional commands, e-mail: dev-help@artemis.apache.org