non- persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle). You will have will be automatically recreated when broker restarts and repopulated with a new, auto-generated node ID. 3. If you're using JGroups then due to the changes in ARTEMIS-2413 where JGroups was updated

non- persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle). You will have will be automatically recreated when broker restarts and repopulated with a new, auto-generated node ID. 3. If you're using JGroups then due to the changes in ARTEMIS-2413 where JGroups was updated

non- persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle). You will have will be automatically recreated when broker restarts and repopulated with a new, auto-generated node ID. 3. If you're using JGroups then due to the changes in ARTEMIS-2413 where JGroups was updated

non- persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere message production and consumption (in recommended order): i. Use a metrics plugin. This is the most feature-rich and flexible way to track broker metrics, although it requires tools (e.g. Prometheus) to store was a light release. It included a handful of bug fixes, a few improvements, and one major new feature. Highlights: Support exporting metrics. 2.8.1 Full release notes. This was mainly a bug-fix

non- persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere message production and consumption (in recommended order): i. Use a metrics plugin. This is the most feature-rich and flexible way to track broker metrics, although it requires tools (e.g. Prometheus) to store was a light release. It included a handful of bug fixes, a few improvements, and one major new feature. Highlights: Support exporting metrics. 2.8.1 Full release notes. This was mainly a bug-fix

non- persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle). You will have will be automatically recreated when broker restarts and repopulated with a new, auto-generated node ID. 2.20.0 Full release notes. Highlights: Java 11 is now required. 2.19.0 Full release notes

non- persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle). You will have will be automatically recreated when broker restarts and repopulated with a new, auto-generated node ID. 2.20.0 Full release notes. Highlights: Java 11 is now required. 2.19.0 Full release notes

non- persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere message production and consumption (in recommended order): i. Use a metrics plugin. This is the most feature-rich and flexible way to track broker metrics, although it requires tools (e.g. Prometheus) to store was a light release. It included a handful of bug fixes, a few improvements, and one major new feature. Versions 16 Highlights: Support exporting metrics. 2.8.1 Full release notes. This was mainly

non- persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere message production and consumption (in recommended order): i. Use a metrics plugin. This is the most feature-rich and flexible way to track broker metrics, although it requires tools (e.g. Prometheus) to store was a light release. It included a handful of bug fixes, a few improvements, and one major new feature. Highlights: Support exporting metrics. 2.8.1 Full release notes. This was mainly a bug-fix

for non-persistent messaging, our non-persistent messaging performance rocks the boat too. Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere in ARTEMIS-3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle). You will have it will be automatically recreated when broker restarts and repopulated with a new, auto-generated node ID. 3. If you're using JGroups then due to the changes in ARTEMIS-2413 where JGroups was updated