Hi Nacho- Thank you for the follow up! Glad to hear the upgrade is done, and you are converted to the new jetty configuration approach. I believe that having ActiveMQ follow the upstream Jetty-style for configuration will serve everyone better going forward, so glad to hear that is in place for you.
Thanks! Matt Pavlovich > On Oct 7, 2026, at 1:33 AM, Nacho Barrientos via dev > <[email protected]> wrote: > > Hi Matt, all, > > On 27/09/26, Matt Pavlovich said: >> Sounds good, let us know if you have any hiccups with the upgrade. For >> sure look into the changes related to Jetty if you use the console >> and/or REST APIs. >> >> The new Jetty configuration approach in 6.3.x is hardened to use >> native Jetty configuration files instead of mapping Jetty setup using >> Spring. This will be easier to maintain and ensure proper security >> hardening going forward. > > Many thanks for the heads-up. We completed the upgrade yesterday and > indeed it's been a bit laborious to prepare as we had to completely > rewrite and validate again our Jetty configuration. > > Anyhoo, everything went fine, I reckon. > > With immense gratitude to all the maintainers, > > -- > bye > Nacho > http://cern.ch/nacho > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
