Back to blog

OSSeva Blog

Operations

ActiveMQ Support Providers Compared: Classic and Artemis

Matt ReynoldsUpdated 10 min read

The short answer

Five providers publish ActiveMQ support. Red Hat sells AMQ Broker, its own product built on Apache Artemis (7.14 is based on Artemis 2.53.0). Amazon MQ runs ActiveMQ Classic 5.18 and 5.19 as a managed service. Perforce OpenLogic and meshIQ sell 24/7 support contracts for ActiveMQ Classic and Artemis, and meshIQ also sells Classic to Artemis migration. OSSeva ships patched builds of Classic 5.15 to 5.18 and Artemis 2.28 to 2.32, the lines Apache no longer fixes, and can run the brokers for you.

For the OSSeva offer itself, ActiveMQ Classic support shows which lines Apache still fixes and how the Artemis move compares.

The question that separates them is what happens to a broker on a line Apache has stopped releasing. Only some of these providers publish new security fixes for those lines; the others help you run or replace them.

OSSeva publishes this list and is one of the five providers in it. Every other provider fact comes from that provider's own site, checked 8 November 2026. OSSeva's row comes from our own ActiveMQ Classic and Artemis pages.

In short:

  • Apache fixes only Classic 5.19, 6.3 and 6.4 and the newest Artemis release; every other Classic line is marked inactive.
  • Apache's own support page lists companies that sell ActiveMQ support; four of them are compared here, plus OSSeva.
  • Only some providers publish new security fixes for lines Apache has stopped releasing. The others help you run, upgrade or replace those brokers.
  • OSSeva covers Classic 5.15 to 5.18 and Artemis 2.28 to 2.32 and is not the right fit for every case. A section below says when to pick someone else.

Running ActiveMQ Artemis in production? OSSeva patches and supports it, end-of-life versions included.

Who provides commercial support for Apache ActiveMQ?

Apache ActiveMQ is a project of the Apache Software Foundation, which offers free community support but not commercial support. Apache's own support page lists the companies that sell it, including Red Hat, Amazon Web Services, OpenLogic and meshIQ. This comparison covers those four and OSSeva.

Apache's page names eleven companies in all. The other seven are apifocal, Avada Software, HYTE Technologies, Savoir Technologies, Total Transaction Management, Tomitribe and Yupiik. We did not review their own sites, so they are not in the tables. OSSeva is not on Apache's list.

Best for: which provider fits which situation

ProviderBest forVersions coveredSupport model
Red Hat AMQ BrokerTeams already on RHEL or OpenShift that are moving to ArtemisAMQ Broker 7.14, based on Artemis 2.53.0 (7.13 was based on 2.40.0); Java 17, 21 and 25. It is built on Artemis, not on ActiveMQ ClassicRed Hat subscription; tested on RHEL 8, 9 and 10 and on OpenShift
Amazon MQ for ActiveMQClassic brokers that you want AWS to run and upgrade for youClassic 5.19 (recommended) and 5.18; 5.15 to 5.17 retired; its version page lists no 6.x and no ArtemisManaged service on AWS; brokers upgrade automatically after a version's end of support
Perforce OpenLogicA 24/7 support desk for ActiveMQ and Artemis, with architects and training"ActiveMQ and Artemis"; no version list published; ActiveMQ is not on its long-term support list of patched buildsSLA-backed support subscription, 24/7/365
meshIQClassic or Artemis brokers that need 24/7 incident response, or a planned move from Classic to ArtemisActiveMQ 5.x and 6.x, Artemis 2.x and Camel 4.x; planning help for end-of-life lines such as 5.14 and 5.1524/7/365 incident response with named engineers; P1 acknowledged within one hour, with service credits if missed
OSSevaClassic 5.15 to 5.18 or Artemis 2.28 to 2.32 brokers that Apache no longer fixesClassic 5.15, 5.16, 5.17 and 5.18; Artemis 2.28 to 2.32Subscription in three tiers (Patch, Assure, Operate), priced per cluster; signed Maven artifacts, Docker images and tarballs; Operate adds 24/7 monitoring and a 15-minute P1 response

How we chose these providers

ActiveMQ is two Apache projects, Classic and Artemis, and Apache supports only the newest lines of each. So the test for this list is what a provider does for a broker on a line Apache has stopped releasing. We kept a provider if it passed all three of these, and OSSeva was held to the same ones.

  1. It names ActiveMQ Classic, Artemis or a product built on Artemis. A page on its own site, not a general claim about open source messaging.
  2. It states what it does for older lines. That can be patched builds (OSSeva), CVE patching without a version list (meshIQ), a supported product with its own lifecycle (Red Hat), automatic upgrades (Amazon MQ) or support without a patch claim (OpenLogic). Each row says which, so you can see the difference between them.
  3. It is on sale on 8 November 2026, with the claims checkable on the provider's own site.

Apache itself is not a row: the Apache Software Foundation publishes releases, not commercial support. We compared what providers publish, without running their services or auditing their claims. A provider missing from this list is one we did not verify, not one we judged unfit, and the order of the rows is not a ranking.

Which ActiveMQ versions Apache still maintains

ActiveMQ is now two Apache Software Foundation projects. The ActiveMQ PMC voted on 19 November 2025 to make Artemis a separate top-level project, so Classic lives at activemq.apache.org and Artemis at artemis.apache.org, each with its own releases. Until that vote Artemis was developed under the ActiveMQ project, which is why it is still widely called ActiveMQ Artemis.

LineStatus on 8 November 2026Latest releaseNotes
ActiveMQ Classic 6.4.xActive6.4.0 (27 October 2026)Jakarta Messaging; first release of the line
ActiveMQ Classic 6.3.xActive6.3.3Jakarta Messaging; Java 17, 21 and 25
ActiveMQ Classic 6.2.xInactive6.2.10Marked inactive on the Apache download page
ActiveMQ Classic 6.1.xInactive6.1.8Marked inactive on the Apache download page
ActiveMQ Classic 5.19.xActive5.19.12javax.jms; Java 11, 17 and 21
ActiveMQ Classic 5.18.xInactive5.18.7 (19 March 2025)Marked inactive on the Apache download page
ActiveMQ Classic 5.17.x and earlierInactive5.17.7, 5.16.8, 5.15.16No upstream fixes
Apache Artemis 2.xLatest release2.57.0Fixes ship in new 2.x releases; Apache publishes no support window for earlier ones

Apache's download page defines an inactive line as one that has "reached end-of-life and is no longer actively maintained". The ActiveMQ Classic and Artemis end-of-life charts track every line, and ActiveMQ vulnerabilities by version lists the advisories that reach the inactive ones.

ActiveMQ support providers compared

Each row reflects what the vendor publishes on its own site as of 8 November 2026.

ProviderWhat it coversVersionsDelivery modelSelf-managed?
Red Hat AMQ BrokerRed Hat's own broker product built on Apache Artemis, supported on OpenShiftAMQ Broker 7.14, based on Artemis 2.53.0; 7.13 was based on 2.40.0; Java 17, 21 and 25Red Hat subscription; tested on RHEL 8, 9 and 10 and OpenShift 4.14 to 4.21Yes, on Red Hat platforms
Amazon MQ for ActiveMQManaged ActiveMQ Classic brokers, including ActiveMQ's network of brokers feature, with automatic upgrade to the next supported version when a version reaches end of support on Amazon MQClassic 5.18 and 5.19; 5.15 to 5.17 already retired; no 6.x and no ArtemisManaged service on AWSNo
Perforce OpenLogic24/7/365 SLA-backed technical support, with help on configuration and JVM tuning, Enterprise Architects and training; not on its patched long-term support listActiveMQ Classic and Artemis; no version list publishedSupport subscriptionYes
meshIQ24/7/365 incident response with named engineers, CVE patching and security hardening, network-of-brokers configuration, proactive monitoring, and zero-downtime migration to ArtemisActiveMQ 5.x and 6.x, Artemis 2.x; advisory and migration planning for end-of-life lines such as 5.14 and 5.15Support subscription and servicesYes
OSSevaBackported security fixes for Classic, with OpenWire and STOMP CVEs prioritised and patched client libraries; Artemis CVE patches across AMQP, OpenWire, MQTT and STOMP; network-of-brokers topology review, migration assessment and 24/7 operations on higher tiersClassic 5.15, 5.16, 5.17 and 5.18; Artemis 2.28 to 2.32Signed Maven artifacts, Docker images and tarballsYes

Two rows need reading closely. Amazon MQ upgrades brokers itself when a version reaches end of support on the service, within 45 days and after at least 90 days' notice, so it keeps you current rather than keeping an old version alive. meshIQ lists CVE patching but does not publish which versions receive patched builds, so ask for that in writing before relying on it for an inactive line.

How the providers differ

Red Hat AMQ Broker

Red Hat's product is the closest thing to vendor support for Artemis. Red Hat's version mapping lists AMQ Broker 7.12 on Artemis 2.33.0, 7.13 on 2.40.0 and 7.14 on 2.53.0. It is a Red Hat build, and its supported-configurations page for 7.14 lists RHEL 8, 9 and 10, OpenShift 4.14 to 4.21, and Java 17, 21 and 25. If you already run OpenShift and are moving to Artemis, it is the natural choice. It is built on Artemis, not on ActiveMQ Classic. Red Hat's long-term support designations and support dates sit on pages we could not fetch, so check them with Red Hat before you plan around a release.

Amazon MQ

Amazon MQ runs the brokers for you, and with automatic minor version upgrades turned on it moves each broker to the newest patch release during the maintenance window. Its version policy is the important part. Classic 5.15, 5.16 and 5.17 have already been retired on the service, and when 5.18 is retired, brokers move to the next supported version automatically during the maintenance window. Amazon MQ has no Classic 6.x and no Artemis, so it is not a destination for Jakarta Messaging or for an Artemis migration.

Perforce OpenLogic

OpenLogic offers SLA-backed support for ActiveMQ and Artemis, with Enterprise Architects, configuration and JVM tuning help, and a two-week virtual ActiveMQ training course. Its long-term support product, which supplies patched builds after end of life, does not list ActiveMQ. Our OSSeva vs OpenLogic comparison covers the wider overlap.

meshIQ

meshIQ sells enterprise support for ActiveMQ 5.x and 6.x, Artemis 2.x and Apache Camel 4.x, with a published P1 acknowledgement time of under one hour and service credits if it is missed. It also offers a free assessment of your broker topology, and a migration service that uses a dual-publish bridge and keeps Classic on standby for 72 hours after cutover.

OSSeva

OSSeva for ActiveMQ Classic backports security fixes onto 5.15, 5.16, 5.17 and 5.18, so a broker stays on the line its integrations, selectors and KahaDB store already work with. Fixes for OpenWire and STOMP transport CVEs and Java deserialization issues are prioritised, and patched activemq-client artifacts ship from the same build so both ends of a connection match. OSSeva for Artemis patches 2.28 to 2.32 across AMQP 1.0, OpenWire, MQTT and STOMP. Assure adds a transport and authentication audit and a costed migration assessment; Operate adds 24/7 queue depth and store monitoring, a 15-minute P1 response and migration execution. Brokers are priced per cluster, not per queue or connection.

Which providers cover a network of brokers?

A network of brokers is an ActiveMQ Classic feature that connects several brokers so queues and topics are distributed across them. Amazon MQ supports it, meshIQ lists network-of-brokers configuration in its tuning work, and OSSeva's Assure tier includes a topology review. Red Hat's AMQ Broker is built on Artemis, which uses clusters instead.

Apache's documentation describes the network of brokers as a way to survive the failure of any one broker, and it also means every broker in the network runs its own copy of the code. A patch plan has to reach each of them, so ask a provider whether its contract counts brokers or clusters, and whether mixed versions inside one network are covered.

Who can help migrate ActiveMQ Classic to Artemis?

Artemis accepts OpenWire clients, so existing JMS applications usually connect on day one. The work is in everything else: Artemis has its own message store in place of KahaDB, a different addressing model, and clusters in place of Classic's networks of brokers, so the topology is a design task and not a copy. Help is available from several directions:

  • meshIQ, which publishes a zero-downtime migration service to Artemis using a dual-publish bridge.
  • Red Hat, which supports the destination broker if you choose AMQ Broker on RHEL or OpenShift.
  • OpenLogic, which supports both brokers, so one contract can cover the old and new estate during the move.
  • OSSeva, which keeps the Classic brokers patched while the migration runs, covers Artemis on the other side, and executes the move on the Operate tier.

Our guide to migrating ActiveMQ Classic to Artemis walks through what changes, and what tends to be underestimated.

Upgrade, migrate or buy extended support?

There are three moves for a broker on an inactive Classic line, and they differ a lot in effort.

MoveRelative effortWhen it fits
Classic 5.x to 5.19Lowest; same javax.jms APIThe quickest way back to upstream fixes for 5.15 to 5.18 brokers
Classic to 6.3 or 6.4Moderate; clients move to jakarta.jmsApplications already moving to Jakarta EE
Classic to ArtemisHighest; a re-platformEstates that will run brokers for years and want the newer engine
Extended support on the current lineLow; no change to clients or topologyBrokers pinned by a vendor product, a change freeze, or a migration that will take longer than the exposure allows

Most estates combine them: move what can move to 5.19 now, keep patched builds on the brokers that cannot, and plan Artemis as a separate project. Brokers on 6.1 or 6.2 have a short path to 6.3 or 6.4, the active Jakarta lines.

When OSSeva is not the right fit

Choose another provider, or no provider, when one of these describes you:

  • Your brokers are on Classic 5.19, 6.3 or 6.4, or on the newest Artemis release. Apache still fixes those lines, so upgrading within them is the plain answer, and OSSeva's patched builds cover the older lines.
  • Your brokers are on Classic 6.0 to 6.2. OSSeva's own page tells those brokers to move to 6.3 or 6.4, because its patched Classic builds are 5.15 to 5.18.
  • You want AWS to run the brokers and handle upgrades: that is Amazon MQ.
  • You run RHEL or OpenShift and want a vendor-built Artemis broker: that is Red Hat AMQ Broker.
  • You mainly want a support desk and training on the version you run today, with no change of build: OpenLogic and meshIQ publish 24/7 support, and OpenLogic lists a two-week ActiveMQ course.

Where OSSeva fits

OSSeva covers the ActiveMQ lines Apache has stopped fixing, Classic 5.15 to 5.18 and Artemis 2.28 to 2.32, with signed builds and the option of 24/7 operations while you migrate. See ActiveMQ Classic extended support for the offer and the extended support vendor roundup for how OSSeva compares by technology layer.

Frequently asked questions

Who provides commercial support for Apache ActiveMQ?

Apache ActiveMQ is an Apache Software Foundation project, and the project itself offers free community support from volunteers. Commercial support comes from companies that Apache's support page lists, including Red Hat, Amazon Web Services (Amazon MQ), OpenLogic and meshIQ. OSSeva also sells it, for the Classic and Artemis lines Apache no longer fixes.

What are the best ActiveMQ extended support providers?

For patched builds of Classic lines Apache no longer fixes, OSSeva publishes coverage for 5.15 to 5.18. For Artemis, Red Hat sells AMQ Broker (7.14 is based on Artemis 2.53.0), and OSSeva patches Artemis 2.28 to 2.32. OpenLogic and meshIQ sell 24/7 support contracts for both brokers, and Amazon MQ runs Classic 5.18 and 5.19 as a managed service.

Which companies provide ActiveMQ maintenance and security patches?

Apache patches Classic 5.19, 6.3 and 6.4 and the latest Artemis release. Red Hat ships fixes for AMQ Broker, its Artemis-based product. OSSeva backports fixes to Classic 5.15 to 5.18 and Artemis 2.28 to 2.32. meshIQ lists CVE patching in its support. Amazon MQ can apply the newest patch release to the brokers it runs, within the versions it supports.

Who provides extended support for ActiveMQ Artemis?

Red Hat, through AMQ Broker (7.14 is based on Artemis 2.53.0). OSSeva, with patched Artemis 2.28 to 2.32 builds that run on any Linux distribution or container platform. OpenLogic and meshIQ offer support contracts for Artemis 2.x.

Who can help migrate ActiveMQ Classic to Artemis?

meshIQ and OSSeva both publish Classic to Artemis migration services, and OSSeva's Operate tier executes the move. Red Hat supports AMQ Broker as the destination, and OpenLogic supports both brokers during the transition. OSSeva can also keep the Classic brokers patched during the move, which keeps the migration on a planned schedule rather than an emergency one.

How do ActiveMQ support SLAs and coverage compare?

meshIQ publishes a P1 acknowledgement time of under one hour with service credits. OSSeva's Operate tier has a 15-minute P1 response. OpenLogic's SLA depends on the support level bought. Red Hat's terms follow its subscription. Coverage differs more than response times: check whether the contract includes new security fixes for the exact version you run.

Is ActiveMQ Classic end of life?

Not as a product. Apache still releases Classic 5.19, 6.3 and 6.4. Every other line, including 5.18, 6.1 and 6.2, is marked inactive and gets no further updates.

Sources

All pages below were checked on 8 November 2026. No prices are quoted.

Tags

ActiveMQArtemisExtended SupportAmazon MQVendor Comparison

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call