Classic to Artemis is a broker change, not an upgrade
ActiveMQ Classic and Artemis are different brokers sharing a name. Artemis speaks OpenWire, which makes the migration look easy -- until the store, the network-of-brokers topology and the operational tooling don't carry over.
Challenge
OpenWire compatibility makes a Classic-to-Artemis move look like a drop-in. The clients connect, so the migration is declared low-risk -- and then the message store format, the broker topology and every piece of operational tooling built around Classic turn out to be different.
Environment
ActiveMQ Classic 5.x carrying production messaging, with a network-of-brokers topology or KahaDB store.
Approach
OSSeva patches the Classic line so it is covered while the Artemis decision is made, and scopes the migration against the store and topology rather than the wire protocol.
What this delivers
A supported Classic broker now, and an Artemis migration scoped against what actually differs.