ActiveMQ support, 24/7

ActiveMQ Support for Classic, Artemis, Amazon MQ and Networks of Brokers

Last reviewed by Tyler Eastridge

AceMQ supports ActiveMQ Classic and ActiveMQ Artemis 24/7, self-managed, on Kubernetes and on Amazon MQ. Most calls start with one of three problems: producers blocked by flow control, a KahaDB journal that will not shrink, or a network of brokers that duplicates or strands messages after a split.

24/7 across Americas, EMEA and APAC, with response targets from 15 minutes, by plan, and a written root cause analysis on every P1.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ ActiveMQ consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

ActiveMQ problems we fix every week

The broker failures behind most ActiveMQ calls, shown with the JMX attribute, config value or log we read before changing a thing.

Common ActiveMQ production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Producers hang with no error (Classic)Producer flow control state; memoryLimit, storeUsage and tempUsage; whether one destination used the shared limit while a slow consumer sat behind itA memoryLimit per destination class, a store cursor so a backlog pages to KahaDB, a sendTimeout on non-critical producers
KahaDB journal grows and the disk fills (Classic)Which journal files are pinned; inactive durable subscribers in JMX holding referencesDestroy abandoned durable subscribers, set an offline durable subscriber timeout, move fan-out to virtual topics
OutOfMemoryError at normal volumeConsumer prefetch against heap; a prefetch of 1000 on large messages across many consumersPrefetch sized for the slowest consumer
Messages loop through redelivery and the DLQ growsRedelivery policy; whether the consumer fails before or after acknowledgement; XA transaction boundariesCorrect the policy, handle poison messages, fix the acknowledgement mode
Duplicates or stranded messages across a network of brokers (Classic)Network connector settings, duplex, networkTTL, conduitSubscriptions, advisory flowCorrect connector settings and TTL
Address full, paging, throughput collapses (Artemis)max-size-bytes, address-full-policy, page-size-bytes against consumer drain rate; paging hides a slow consumerSize address settings, find and fix the slow consumer
Clients do not reconnect to the backupShared-store or replication topology; file lock acquisition; whether the client URI lists the failover transport with both brokersCorrect topology and the failover URI
A scanner flags the broker, or the OpenWire port is reachable too widelyWhich CVEs apply to your version, whether the OpenWire port is exposed beyond known clients, whether client libraries inside fat jars carry the flawRestrict the port first, then upgrade brokers and client libraries

A P1 closes with a report naming the destination, subscriber or limit that caused the stall.

Producers blocked on a production broker? Request a quote and an engineer answers within one hour.

Contact Us

Deployment coverage

Which ActiveMQ deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
ActiveMQ Classic 5.x and 6.x, self-managed24/7 incident response, written RCA on P1s, flow control and store tuning, persistence choice (KahaDB or JDBC), CVE advice, upgradesThe Apache project publishes releases and lists which series are active; it offers community help only (activemq.apache.org, read 17 Nov 2026)Application code and Camel routes are reviewed, not rewritten
ActiveMQ Artemis 2.xAddress settings, paging, journal, HA topology, upgradesThe Apache Artemis project (artemis.apache.org)The same
Red Hat AMQ BrokerThe Artemis behaviour underneath: addresses, paging, clientsRed Hat supports AMQ Broker for subscribersA patched Red Hat build
Amazon MQ for ActiveMQDestination design, prefetch and memory tuning, client failover configurationAWS runs and supports the serviceAWS platform faults, broker settings the service does not expose
Kubernetes, OpenShift, vSphere and TanzuPod and volume behaviour as it affects journals and stores, failover, rolling restartsThe platform vendor supports the platformControl-plane faults
Networks of brokers, JDBC storesConnector design, advisory behaviour, database contention on the storeThe database vendor supports the databaseDatabase engine faults
Protocol clients (OpenWire, AMQP, STOMP, MQTT, JMS)Client configuration and compatibility, including Jakarta Messaging movesNoneWriting client applications

Support options

Who provides commercial support for Apache ActiveMQ? Vendor and independent support compared

Apache ActiveMQ is an open-source project with community help only. Commercial support comes from Red Hat for AMQ Broker, from AWS for Amazon MQ as a managed service, and from independent providers such as AceMQ for the Apache releases you run yourself.

Red Hat (AMQ Broker) / AWS (Amazon MQ) / Apache project
AceMQ independent support
CoversRed Hat (AMQ Broker): Red Hat's own AMQ Broker, built on ActiveMQ ArtemisAWS (Amazon MQ): The managed serviceApache project: ActiveMQ Classic and Artemis releases
CoversApache ActiveMQ Classic and Artemis, and the workload layer on Amazon MQ
Product defectsRed Hat (AMQ Broker): Red Hat can fix its own buildAWS (Amazon MQ): AWS fixes the serviceApache project: Project release process
Product defectsWe diagnose and work the upstream or vendor escalation
Operational issues (flow control, KahaDB, prefetch)Red Hat (AMQ Broker): Within plan scopeAWS (Amazon MQ): Yours to configureApache project: Community help
Operational issues (flow control, KahaDB, prefetch)Core of our work
PriceRed Hat (AMQ Broker): Red Hat subscriptionAWS (Amazon MQ): AWS usageApache project: Free
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour

What's Included

Everything in your ActiveMQ support contract

Classic and Artemis brokers, KahaDB or journal persistence, networks of brokers and failover pairs, covered by one agreement without per-incident fees.

  • 01

    Emergency Incident Response

    Production down, messages not flowing, or a broker that won't start. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with direct access to diagnose — not a ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the specific configuration or code change that prevents recurrence. Delivered as standard, not on request.

  • 03

    Performance Tuning

    Prefetch sizing, memory and store limits, KahaDB vs. JDBC persistence selection, and consumer concurrency tuned against your actual throughput profile and message sizes.

  • 04

    CVE & Patch Advisory

    Proactive alerts for CVEs affecting your exact ActiveMQ version — including the 2023 CVE-2023-46604 class of RCE issues — with tested upgrade paths and mitigation guidance.

  • 05

    Capacity & Scaling Reviews

    Quarterly reviews of queue depth trends, broker resource headroom, and destination growth so you size ahead of demand rather than reacting to a full store.

  • 06

    Upgrade & Migration Support

    ActiveMQ Classic to Artemis migration planning, version upgrades with rolling procedures, and migration off ActiveMQ to RabbitMQ or Kafka where that's the right call.

Why AceMQ

Why Java and messaging teams keep AceMQ close

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your broker topology, your persistence choice, and your traffic pattern — so a P1 call starts with diagnosis, not twenty minutes of you explaining your environment.

  • No Tier-1 Triage Layer

    You reach a senior ActiveMQ engineer directly by phone, email, or Slack. There is no help desk collecting information to pass along, and no escalation approval process standing between you and someone who can actually fix it.

  • Classic and Artemis, Both Deeply

    Most vendors know one. We support ActiveMQ Classic 5.x and Artemis 2.x in production, including the migration between them — which matters because the two share a name and almost nothing else architecturally.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am incident is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

  • Proactive, Not Just Reactive

    Quarterly health checks on your deployment plus shared intelligence across our support base. When a version-specific bug surfaces on one customer's cluster, every affected customer hears about it before it reaches their production.

  • Full-Stack, Not Just the Broker

    ActiveMQ problems are often not ActiveMQ problems. We diagnose across the JVM, the OS, storage latency, network policy, and Kubernetes — because that's where the root cause frequently actually lives.

ActiveMQ deployments we cover

Self-managed brokers, Amazon MQ, Kubernetes, pairs sharing a store, and locked-down sites that cannot reach out to us.

  • AWS (EC2, ECS, EKS)
  • Microsoft Azure (AKS)
  • Google Cloud (GKE)
  • Amazon MQ for ActiveMQ
  • Kubernetes & OpenShift
  • VMware vSphere & Tanzu
  • Bare metal & on-premise
  • Hybrid cloud
  • Air-gapped / no outbound access
  • ActiveMQ Classic 5.x
  • ActiveMQ Artemis 2.x

Version coverage

ActiveMQ versions we support

ActiveMQ versions we support
SeriesLatest listed (activemq.apache.org / artemis.apache.org, read 17 Nov 2026)JavaWhat AceMQ does on it
Classic 6.4.x6.4.0, 27 Oct 2026; listed as active17 and later24/7 support; the target for upgrades from 5.x
Classic 6.3.x6.3.3, 27 Oct 2026; listed as active17, 21, 2524/7 support
Classic 6.2.x, 6.1.x, 6.0.x6.2.10 (26 Sep 2026); 6.1.8; 6.0.1; listed as inactive17 and later24/7 support and an upgrade plan to an active series
Classic 5.19.x5.19.12, 27 Oct 2026; listed as active11, 17, 2124/7 support
Classic 5.18.x and earlier5.18.7 and earlier; listed as inactivePer series24/7 support and an upgrade plan to an active series
Artemis 2.x2.57.0, 9 Sep 202617 and later24/7 support

Classic 6.x moves from the javax.jms namespace to Jakarta Messaging and needs Java 17, so an upgrade from 5.x touches application code and libraries as well as the broker. We inventory clients first, then upgrade brokers and clients in an order that keeps failover working.

In practice

Classic or Artemis: what changes the day-two work

The two brokers need different skills. We ask which you run before anything else.

Classic or Artemis: what changes the day-two work
TopicActiveMQ ClassicActiveMQ Artemis
PersistenceKahaDB journal or a JDBC storeAppend-only journal with paging to disk
Memory pressureProducer flow control against memoryLimit, storeUsage, tempUsageaddress-full-policy and paging
HAShared-store master and slave, or networks of brokersShared store or replication, with live and backup pairs
Native protocolOpenWire (also AMQP, STOMP, MQTT)Core protocol (also AMQP, STOMP, MQTT, OpenWire)
First place we look in an incidentBroker log and JMX for destination memory and store usageAddress and queue metrics, paging state

Consulting

ActiveMQ consulting and professional services

ActiveMQ consulting and professional services
DeliverableWhat you receive
Broker health checkMemory, store and temp limits per destination, prefetch against heap, durable subscriber audit, failover test, version and CVE position
Performance tuningPer-destination limits, cursor choice, prefetch sizing, persistence choice from measured throughput
Security reviewExposure of transport connectors, authentication and TLS on connectors, client library inventory, advisory monitoring
Upgrade plan5.x to 6.x with the Jakarta namespace move, Classic to Artemis planning, rehearsal and rollback
Migration planningMoves from ActiveMQ to RabbitMQ or Kafka with protocol mapping, parallel running and canary cutover, where migration fits
RunbooksFinding the slow consumer from JMX, clearing a pinned journal, failing over safely

Escalation Path

Your first hour of an ActiveMQ outage

Blocked producers do not log an error, so whoever picks up the page has to know to check flow control first.

  1. From 15 min (by plan)first responseEmergencyEvery producer blocked on a production broker, a broker refusing to start, or a failover pair where neither side serves clients
  2. 1 hourfirst responseCriticalOne backlog throttling unrelated queues, KahaDB store near its limit, an exposed OpenWire port with a known CVE
  3. 4 hoursfirst responseHighA redelivery loop on a single consumer, a durable subscriber growing without bound, Artemis paging after address full
  4. Next Dayfirst responseStandardPrefetch guidance for a new consumer, a 5.x to 6.x upgrade plan, failover test design

A broker that will not start gets the fastest clock; advice on prefetch for a new consumer waits in a slower queue.

Want engineers who already know your destinations and failover setup? Request a quote or write to us.

Contact Us

Pricing

What does AceMQ ActiveMQ support cost?

ActiveMQ support usually costs $24,000–72,000 a year. The figure depends on whether you run Classic or Artemis, how many brokers and networks of brokers there are, KahaDB or JDBC persistence, and the response target you need.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests are answered within 1 hour. Adding Artemis or Classic brokers, Kafka or other messaging to one contract earns a multi-technology discount.

Support In Practice

ActiveMQ failures we have worked through

ActiveMQ support and migration work from AceMQ. Each card links to the full write-up: the broker estate, what AceMQ diagnosed or changed, and the result.

All use cases

Support options

Four tiers of ActiveMQ support.

AceMQ offers ActiveMQ support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for brokers your team runs, proactive monitoring that catches store, memory and CVE problems first, managed ActiveMQ on your own infrastructure, and fully managed Artemis on AceMQ infrastructure. Classic 5.x, 6.x and Artemis 2.x are covered in all four.

  • Tier 1

    ActiveMQ 24/7 Support & Incident Management

    Your team owns the brokers, we escalate

    Best for: Application teams running Classic or Artemis who need a broker specialist when flow control or failover goes wrong.

  • Tier 2

    ActiveMQ 24/7 Support with Proactive Monitoring

    Regular broker audits and failover tests

    Best for: Groups that want durable subscribers, store usage and exposed connectors checked before they cause an outage.

  • Tier 3

    Managed ActiveMQ on Your Infrastructure

    We operate your brokers in your environment

    Best for: Companies whose brokers must stay on their own hosts or private network, but whose team is stretched thin.

  • Tier 4

    Fully Managed ActiveMQ on AceMQ Infrastructure

    We run your ActiveMQ brokers as a service

    Best for: Teams who rely on JMS messaging but would rather not run the brokers, stores and failover themselves.

FAQ

ActiveMQ support questions

Still have questions about ActiveMQ? Email an Expert

Who provides commercial support for Apache ActiveMQ?

The Apache project offers community help only. Red Hat supports AMQ Broker, its own product built on ActiveMQ Artemis, and AWS supports Amazon MQ as a managed service. Independent providers such as AceMQ support the Apache releases themselves, Classic and Artemis, on premises, in the cloud or on Kubernetes, 24/7, with response targets from 15 minutes, by plan.

What does 24/7 ActiveMQ support cover with AceMQ?

Round-the-clock response from 15 minutes on the top plans. For a Sev 1 where producers are blocked, an engineer joins a bridge, reads flow control state and store usage, and you receive a written root cause. Standing work includes subscriber audits, failover tests and upgrade planning.

Do you support both ActiveMQ Classic and Artemis?

Yes. They share a name and have different architectures, persistence models and configuration. We support Classic 5.x and 6.x and Artemis 2.x in production, and plan the migration between them.

Why are my ActiveMQ producers blocked?

Almost always producer flow control. A destination hit its memory limit, usually because a consumer is slow, and the broker throttles senders. In Classic we check memoryLimit, store and temp usage and prefetch, then add per-destination limits and a store cursor.

Why is my KahaDB journal growing without bound?

A journal file is deleted only when no message in it is still needed, and one retained message can pin a whole file. The usual holder is an inactive durable subscriber or one unacknowledged message. We find it from JMX and fix the cause.

Can you support ActiveMQ on Amazon MQ?

Yes. Amazon MQ removes some operations, but flow control, prefetch, destination design and client failover remain yours, and they cause most incidents.

Should we upgrade from ActiveMQ 5.x to 6.x?

Plan it. Apache lists 6.4.x, 6.3.x and 5.19.x as active series. Classic 6.x needs Java 17 and uses Jakarta Messaging, so the upgrade touches application code. ActiveMQ has had serious flaws, including the widely exploited OpenWire remote code execution issue CVE-2023-46604, so we restrict exposure, put mitigations in place and support the version you run while the upgrade is prepared.

Which protocols does ActiveMQ support, and does support cover them?

Classic speaks OpenWire natively plus AMQP, STOMP and MQTT; Artemis adds its core protocol. Both implement JMS. Support covers these, Camel routes, JDBC or KahaDB persistence, networks of brokers and Java client configuration.

Can you help us migrate off ActiveMQ?

Yes, and we say whether you should. We plan migrations to RabbitMQ or Kafka with protocol mapping, parallel running and canary cutover, and we often advise that a fixable ActiveMQ is cheaper than a migration.

What does an ActiveMQ health check include?

We read memory, store and temp usage per destination, prefetch against heap, the durable subscriber list, failover behavior, exposed connectors, and your version's known CVEs. The result is a ranked plan with the first fixes marked.

Who offers ActiveMQ consulting and professional services?

Red Hat and AWS consult on their own products, while AceMQ consults on Apache ActiveMQ itself, Classic and Artemis. The consultants also cover the 24/7 rota, so their designs account for how brokers actually fail.

Do you support end-of-life ActiveMQ versions?

Yes. We support legacy ActiveMQ versions that no longer receive upstream patches, including bug workarounds and backported mitigations where official fixes are unavailable. Many regulated environments cannot upgrade on the community's timeline, and that constraint is a normal part of enterprise support rather than a disqualifier. For security fixes on ActiveMQ Classic 5.15 to 5.18 and on Artemis, AceMQ's OSSeva platform backports CVE patches, so an estate can stay on its version while the upgrade is planned.

Do we need a yearly ActiveMQ agreement?

No. A one-off broker health check, a stuck-journal cleanup or a 5.x to 6.x upgrade plan can be bought alone. If you later want 24/7 cover and named engineers who know your destinations and clients, the annual option continues from that work.

How do you price ActiveMQ support?

Contracts range from $24,000 to $72,000 a year (USD). We weigh Classic against Artemis, the number of brokers and environments, whether they run as a single node, a failover pair or a network of brokers, and your response level. Share the topology and a quote follows within 1 hour.

Let's talk

Find the Slow Consumer Before It Blocks Every Producer

Send us your ActiveMQ version, Classic or Artemis, and your broker topology. We reply to quote requests within 1 hour.

A senior ActiveMQ engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email an ActiveMQ Architect