Hi Endre- Technically speaking, this current release set covers that last known compatibility issue where typed exceptions where being downcast to simple JMSException when doing a javax <-> jakarta conversion. For example, a ResourceAllocationException (for producer flow control) would come across as a standard JMSException instead.
This is now handled, so all specific exceptions should be mapped properly between client and broker version(s). I’m trying to keep this page current with Jakarta/JMS 2.0 issues and notes: https://activemq.apache.org/jms2 This is the issue to be sure to have in 6.x and 5.x clients: - Mapping javax / jakarta exception in openwire protocol I’d love to get more feedback from users, such as yourself, on real world scenarios. Thanks! Matt Pavlovich > On Mar 17, 2024, at 5:58 AM, Endre Stølsvik <en...@stolsvik.com> wrote: > > 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 >>
