Hi! Thanks for the release! I have a question wrt. upgrading a 50+ microservice solution: How is the compatibility between old JMS clients (5.x) towards the 6+ server versions?
I guess the wire protocol doesn't care one bit wrt. javax./jakarta? But do the ActiveMQ team have any suggestion wrt. such an upgrade situation? Are there any "guarantees" wrt. the future compatibility between client versions and server versions? I ask since any such compatibility guarantee would put my mind a bit more at ease wrt. doing the upgrade in a rolling fashion. We do obviously have a test env, but knowing whether there is any intention, or not, wrt. compatibility, would be of value. The problem is of course that the jakarta-situation is a bit .. large. Both the JMS libs, the Servlet libs, and Spring, pretty much have to be done "in one go". So knowing what works with what is of value in setting up a transition path. Thanks, Endre On Sun, Mar 17, 2024 at 11:38 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > The ActiveMQ team is pleased to announce Apache ActiveMQ 6.1.0 release. > > It's a new milestone, bringing: > - New JMS 2/3 operations support > - Mapping javax / jakarta exception in openwire protocol > - Add destination field on the job scheduler > - Add org.apache.activemq.broker.BouncyCastleNotAdded property to > control the bouncycastle addition in BrokerService classloader > - A lot of dependency upgrades (Spring 6.1.4, log4j 2.23.0, Jetty 11.0.20, > …) > - ... and much more ! > > You can find details on the Release Notes: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12353745 > > You can download ActiveMQ 6.1.0 here: > https://activemq.apache.org/components/classic/download/ > > Enjoy! > > Regards > -- > The Apache ActiveMQ team >
