> I am a little concerned about how this reflects production readiness...
I just wanted to address this point generally before moving to the specifics... The ActiveMQ community (and Apache in general) is dedicated to producing high-quality, production-ready software, but mistakes inevitably are made. There are bugs in the documentation, code, build processes, etc. Ultimately, the software is provided "as is" as noted in Apache License under which ActiveMQ is distributed. It's also worth noting that the support provided on the public mailing lists is community support [1] provided for free on a volunteer basis. There are commercial support options available with varying service-level agreements which may provide you additional production readiness guarantees. > ...given there are no schema changes mentioned in the upgrade notes... This was certainly missed in the upgrade instructions. I'll change the documentation to reflect the required adjustments to make when upgrading. > ...and it looks to me like it’s backwards incompatible so it couldn’t be done live before the upgrade? That's correct. Any brokers accessing that table would need to be stopped, the node-manager-store table would need to be dropped (or altered to use the new column type). If the table is dropped then when the newly-upgraded broker starts it will automatically re-create that table. Generally speaking, a database is not a very good fit for a message store and therefore it is used *much* less often than the default file-based journal. For this simple reason issues with it are less likely to be discovered. Justin [1] https://activemq.apache.org/support On Tue, May 31, 2022 at 12:29 PM Stephen Baker < stephen.ba...@rmssoftwareinc.com> wrote: > Thanks, > > I am a little concerned about how this reflects production readiness given > there are no schema changes mentioned in the upgrade notes and it looks to > me like it’s backwards incompatible so it couldn’t be done live before the > upgrade? > > If this were a production system what would the recommended upgrade path > be? >
