OSSEVA FOR ACTIVEMQ ARTEMIS
ActiveMQ Artemis support — patched, protected, operated.
OSSeva provides ActiveMQ Artemis support for 2.28.x to 2.32.x, including patched builds for older releases that no longer get upstream fixes, since upstream fixes land on the newest release only. ActiveMQ Artemis is the messaging backbone for thousands of enterprise Java applications. OSSeva provides CVE-patched builds, architectural support, and 24/7 managed operations for 2.x — the production version running in your environment today.
Reply within 1 business day · No commitment · or book a 15-minute call
Last reviewed
Trusted globally by enterprises
Why now
Upstream Artemis and Red Hat AMQ run on different clocks
Artemis became its own Apache top-level project in November 2025 and ships frequently, with 2.57.0 released in September 2026, while Red Hat AMQ Broker 7.13 LTS is built on Artemis 2.40.0. Upstream fixes land on the newest release only, so brokers pinned to an older community release, or between the two release streams, need their own patch plan.
JMS and AMQP 1.0 vulnerabilities affect payment and integration workloads
ActiveMQ Artemis handles JMS message routing in financial services, healthcare, and enterprise integration platforms. CVEs in the message parsing and authentication layers carry direct compliance implications under PCI DSS and HIPAA.
Legacy ActiveMQ 5.x migration creates compliance gaps
Many enterprises are mid-migration from ActiveMQ Classic 5.x to Artemis 2.x. During migration windows, both versions require CVE coverage — a gap most commercial vendors won't address. OSSeva covers both.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 2.28.x | Extended | Clean |
| 2.29.x | Extended | Clean |
| 2.30.x | Extended | Clean |
| 2.31.x | Extended | Clean |
| 2.32.x | Extended | Clean |
Running a ActiveMQ Artemis version or build not listed here?
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
CVE patches for Artemis 2.x. Signed builds, all supported versions.
- Quarterly CVE patches for Artemis 2.28.x–2.32.x
- JMS, AMQP 1.0, MQTT, STOMP protocol coverage
- Maven / Docker delivery
- Signed artifacts (GPG)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus HA architecture review and compliance documentation.
- Everything in Patch
- Live-live HA cluster architecture review
- Message address / queue security audit
- SOC 2 / PCI DSS attestation package
- ActiveMQ Classic → Artemis migration assessment
- AMQP 1.0 configuration hardening guide
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min SLA, named JMS engineers.
- Everything in Assure
- 24/7 broker health monitoring
- 15-minute P1 incident response SLA
- Named senior Artemis engineer on your account
- Queue depth and consumer lag alerting
- Quarterly broker performance reviews
- ActiveMQ Classic migration execution
All tiers priced per cluster/application — not per core.
How it installs
OSSeva artifacts arrive via your existing package infrastructure. Pull the patched version the same way you pull upstream today — just from the OSSeva registry.
docker pull artifacts.osseva.io/activemq-artemis:2.31.2-osseva-1
docker run -d \
--name artemis-broker \
-p 61616:61616 \
-p 8161:8161 \
-e ARTEMIS_USER=admin \
-e ARTEMIS_PASSWORD=changeme \
artifacts.osseva.io/activemq-artemis:2.31.2-osseva-1<dependency>
<groupId>io.osseva.activemq</groupId>
<artifactId>artemis-jms-client</artifactId>
<version>2.31.2-osseva-1</version>
</dependency>Migrate from Red Hat AMQ Broker / IBM MQ
Red Hat AMQ Broker is built on Artemis but requires RHEL subscriptions for support. IBM MQ customers seeking a cost-effective migration path can move to OSSeva-supported Artemis without proprietary lock-in.
Pricing model
OSSeva for Artemis is priced per broker cluster — not per connection or per message. Book a discovery call for a quote.
What protocols does OSSeva cover for ActiveMQ Artemis?
OSSeva CVE coverage includes the full Artemis protocol stack: AMQP 1.0, OpenWire (JMS), MQTT 3.1/5.0, STOMP, and the management console (Hawtio-based). Protocol-specific CVEs in each transport are within scope.
We're on ActiveMQ Classic 5.x. Can OSSeva support both during migration?
Yes. OSSeva can provide simultaneous coverage for ActiveMQ Classic 5.x and Artemis 2.x during your migration window. This dual-coverage engagement is common for customers whose migration is large enough to run in stages; its length depends on broker count, client code volume and the downtime window.
Does OSSeva cover the embedded Artemis broker in Spring Boot?
Yes. Spring Boot embeds Artemis when you include spring-boot-starter-artemis. OSSeva's Spring Boot coverage includes the embedded Artemis version — you get patched builds for both the application framework and the embedded broker.
How does OSSeva compare to Red Hat AMQ Broker support?
Red Hat AMQ Broker support requires RHEL or OpenShift subscriptions and has restrictions on supported deployment environments. OSSeva covers Artemis on any Linux distribution, any container platform, any cloud provider — without platform lock-in.
What does the live-live HA architecture review cover?
The Assure-tier architecture review covers: live-live vs live-backup HA configuration, journal mode selection (ASYNCIO vs NIO), network partition handling, acceptor configuration security hardening, and queue/address security model review.
Who provides ActiveMQ Artemis support besides Apache?
The Apache ActiveMQ project ships Artemis releases, and Red Hat AMQ Broker is a commercial broker built on Artemis that requires RHEL subscriptions for support. Other options are cloud managed broker services and third-party support companies. OSSeva is a third-party option: one contract across your messaging and database stack, older Artemis releases included, and support on any Linux distribution, container platform or cloud provider.
Does OSSeva support current ActiveMQ Artemis versions or only older ones?
OSSeva covers Artemis 2.28.x to 2.32.x, which OSSeva keeps on extended support with patches active. Upstream fixes land on the newest release only, so brokers pinned to an older community release need their own patch plan, and that is what OSSeva provides. Assure adds an ActiveMQ Classic to Artemis migration assessment.
How is OSSeva ActiveMQ Artemis support priced?
OSSeva ActiveMQ Artemis support is priced per broker cluster, not per connection or per message. Patch covers quarterly CVE patches, Assure adds 24/7 reactive support, an HA architecture review and compliance documentation, and Operate adds proactive 24/7 monitoring and managed operations with a 15-minute P1 SLA. OSSeva Operate patches Critical CVEs (CVSS ≥ 9.0) within 48 hours and High within 7 days. Book a discovery call for a quote.
Get a quote
Ready to get ActiveMQ Artemis patched and supported?
Tell us your ActiveMQ Artemis versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?