Commercial support for
Apache ActiveMQ
Your broker moves the data the business runs on, and it breaks at the hour nobody is watching. HYTE supports Apache ActiveMQ versions 6.x and 5.x with patches, architecture review, and no cap on the cases you raise. Our engineers commit code upstream to the project your broker already runs.
Messaging only · Versions 6.x and 5.x · Business hour or 24x7
Messaging is the only thing we do
Most vendors sell support for a catalog of open source projects, and the broker sits on a list beside forty things that share nothing with it. The engineer who picks up your case that week may have spent the prior week in a database.
HYTE works on message brokers and the integrations that feed them. That focus shows up in the answer you get at 2am and in the architecture review you get before anything breaks. When a fix belongs in the broker rather than in your configuration, we write the patch and send it upstream.
Plans start at a single incident and run through a subscription with 24x7 escalation, so a three-server environment and a three-hundred-node platform each get a shape that fits.
What a subscription includes
- Unlimited cases through the HYTE Portal
- Patches for the version you run
- Architecture review with a tenured architect
- Sample code for the patterns your team asks about
- Development, test, and production environments
- Quarterly sessions on prior cases and planning
- Upgrade planning across 5.x and 6.x
Red Hat AMQ 6 support ended in February 2025
Red Hat states in its own documentation that it stopped supporting AMQ 6 in February 2025, and points customers to AMQ 7. AMQ 6 was built on Apache ActiveMQ (formerly called Classic). AMQ 7 is built on Apache Artemis. Two codebases, two brokers, and a move between them that behaves like a migration project rather than an upgrade.
In November 2025 the Apache ActiveMQ PMC voted to establish Apache ActiveMQ and Apache Artemis as separate Top-Level Projects, citing little overlap between the two brokers in developers or users and no goal for either to replace the other. Both projects ship releases. They are siblings, not versions.
Migrating is one option. Staying is another. Nothing forces you off a broker you have trusted with production traffic for years, along with the persistence tuning, the topology, and the runbooks your team wrote after each incident. None of that transfers to a different codebase. Apache ActiveMQ keeps your OpenWire clients, JMS code, destinations, and broker configuration where they sit today, and puts CVE patching back on a schedule.
HYTE supports versions 6.x and 5.x, and our engineers commit code upstream to the project, so the fixes your broker needs come from the same place the code does.
HYTE supports Apache ActiveMQ. Apache Artemis is a separate project with its own community and its own support options. Red Hat and AMQ are trademarks of Red Hat, Inc. HYTE Technologies has no affiliation with Red Hat, Inc.
The code in your broker is code we help maintain
Support shops learn a product from the outside. They read the documentation, they file bugs upstream, and they wait like everyone else for a release that fixes the thing costing you money this quarter.
HYTE sits on the other side of that line. Our engineers commit code upstream to Apache ActiveMQ, which means a fix for your broker starts as a patch we write and ends as a release the whole project ships. The gap between finding a defect and running the fix stops depending on somebody else's roadmap.
Fixes go upstream
A patch that solves your problem lands in the community release, so the next upgrade carries it rather than dropping it.
No fork to maintain
You run Apache ActiveMQ, not a private branch that strands you when the vendor relationship ends.
Roadmap visibility
Upgrade planning starts from what the project is building, not from a guess about the next release.
What the subscription does for your team
Unlimited cases
Administrators, developers, and security each bring different ActiveMQ questions. Every one of them can raise a case.
Patches and CVE fixes
Security work does not wait for your upgrade window. HYTE delivers patches for the version you run.
Hours that fit
Business hour plans for teams that sleep, 24x7 escalation for platforms that do not.
Architecture review
Time with a tenured architect before production, so the design holds when volume triples.
Sample code
Working code answers a developer question faster than a paragraph about the answer.
Every environment
Development, test, staging, and production each carry different risk. Support reaches all of them.
Quarterly sessions
A working review of the quarter’s cases, plus what the project roadmap means for your next year.
Upgrade planning
A sequenced path from 5.x to 6.x, with the client library changes mapped before anyone touches production.
Four teams, four sets of questions
Administrators
Pick the right architecture and build it once. Onboard applications faster with multi-tenant deployments.
Developers
Skip the traps and the features that look useful until production. Questions come back with sample code.
Security
Lock down the broker, encrypt client to broker traffic, authenticate clients, and authorize operations on queues and topics.
DevOps
Package and deploy ActiveMQ builds through your CI/CD pipeline using HYTE templates.
The calls that come in
The broker will not start after an upgrade
A configuration element moved, a dependency changed, or the store needs a migration step. Someone who knows which release changed what shortens this from a day to an hour.
KahaDB grows and will not release disk
One stuck destination or an unacknowledged message holds a journal file, and the journal files behind it stay put. Finding the holder is the work.
Consumers fall behind and memory climbs
Slow consumers, prefetch sizing, and producer flow control interact in ways that show up as a memory graph rather than as an error. Tuning starts with which destination is holding the pages.
A network of brokers splits
Duplicate consumers, message loops, or a store that two brokers both believe they own. Topology and locking settings decide whether this recurs.
TLS fails after a certificate rotation
Truststore contents, cipher suites, hostname verification, and client library versions each break the handshake in a different way. The stack trace rarely names the one that did.
Messages go missing during failover
Acknowledgement mode, transaction boundaries, and redelivery settings determine what survives a broker restart. Most reported message loss turns out to be one of those three.
A decommissioned application left durable subscribers behind
Offline durable subscriptions keep accumulating messages nobody reads, and the store fills on behalf of an application that no longer exists.
An audit asks who can write to which queue
Authentication plugins, authorization maps, and destination wildcards produce an answer that takes reading to reconstruct. Security teams want it in writing.
Something that is not on this list
Two decades of ActiveMQ in production turns up more failure modes than any page can list. Describe what your broker is doing and we will tell you whether it is a configuration problem, a known defect, or a design question. Send us the symptom
Which ActiveMQ releases HYTE supports
6.x
The active release line, built on Jakarta Messaging. Full support, patches, and upgrade guidance.
5.x
Still running in most production environments. Full support, with a planned path to 6.x when your applications are ready.
Pre-5.x and vendor forks
Environments left behind by a discontinued product get triage, interim patching, and a sequenced move onto a supported release.
ActiveMQ Support Essentials and Enterprise
Not every ActiveMQ environment needs a corporate subscription. The Essentials tiers give smaller environments a way in, and Enterprise scales to the platforms that carry the business.
Single Incident
One ticket $995- Support for one ActiveMQ incident
- 9x5 ET availability
- Raised through a HYTE support ticket
Starter Support
One year · 3 servers $4,995- Unlimited tickets through the HYTE Portal
- 9x5 ET availability
- HYTE Console management tools
- Up to 3 ActiveMQ servers
Pro Support
Three years · 3 servers $12,495- Unlimited tickets through the HYTE Portal
- 9x5 ET availability
- HYTE Console management tools
- Up to 3 ActiveMQ servers
- About 17 percent below three annual Starter terms
Enterprise Support
Custom subscription Quoted- 24x7 escalation
- Unlimited servers and environments
- Tooling built around your platform
- Same-day quote after a short call
Your contract may specify different commitment times.
Frequently Asked Questions
Is Apache ActiveMQ still maintained?
Yes. Apache ActiveMQ is an ongoing project at the Apache Software Foundation, with releases in the 6.x line and maintenance work on 5.x. Committers ship features and security fixes through the project’s normal release process. Commercial support sits separate from the project and comes from vendors, including HYTE.
Who provides commercial support for Apache ActiveMQ?
Several vendors sell Apache ActiveMQ support. Most bundle it into a catalog of open source products, so the broker sits alongside dozens of unrelated projects. HYTE supports messaging and the integrations that feed it, and our engineers commit code upstream to Apache ActiveMQ. Plans run from a single incident through a subscription with 24x7 escalation.
Red Hat AMQ 6 reached end of life. What are my options?
Red Hat ended support for AMQ 6 in February 2025 and points customers to AMQ 7. AMQ 6 was built on Apache ActiveMQ and AMQ 7 is built on Apache Artemis, so that path means moving to a different broker rather than upgrading the one you run. The Apache ActiveMQ PMC established the two as separate Top-Level Projects in November 2025, with neither positioned to replace the other. Teams that would rather keep their OpenWire clients, JMS code, and broker configuration can stay on Apache ActiveMQ, and HYTE supports versions 6.x and 5.x with patching, upgrade planning, and architecture review.
Which ActiveMQ versions does HYTE support?
HYTE supports Apache ActiveMQ versions 6.x and 5.x, including builds that no longer draw community attention. Teams on older releases get an upgrade path plus interim patching while they plan the move. Which version you run and which client libraries your applications use both shape the plan, so the specifics belong in a short call.
How do I get CVE patches for Apache ActiveMQ?
Apache publishes fixes through the project’s release process, and teams on current versions pick them up by upgrading. Teams on older builds face a larger jump, which is where a support subscription earns its cost: HYTE delivers a patch for the version you run and sends the fix upstream so it lands in the next community release.
Should I upgrade from ActiveMQ 5.x to 6.x?
ActiveMQ 6.x moved to Jakarta Messaging, which shifts client code from the javax namespace to jakarta. Brokers and clients need to move together, and the sequencing depends on which client libraries your applications import. HYTE plans and reviews these upgrades as part of a support subscription, starting with an inventory of what connects to the broker today.
Is ActiveMQ support available 24x7?
HYTE offers business hour and 24x7 plans. The Essentials tiers, Single Incident, Starter, and Pro, include 9x5 ET availability. Round the clock escalation comes with an Enterprise subscription. Your contract may specify different commitment times.
Are support cases really unlimited?
Yes. Starter, Pro, and Enterprise all include unlimited cases through the HYTE Portal. Teams raise as many as they need, which matters because administrators, developers, security, and DevOps each arrive with a different kind of ActiveMQ question.
What does Enterprise ActiveMQ support include?
Enterprise support is a subscription built around your platform, with 24x7 escalation, unlimited servers, and tooling shaped to your environment. HYTE has designed and supported some of the largest messaging platforms running in production, including at Fortune 500 companies. Subscriptions also carry HYTE Console for broker management and monitoring. A short call produces a same-day quote.
Fifteen minutes with a messaging architect
Bring the broker version, the client libraries, and the thing that woke someone up last month. You will leave with an answer and a price.