Spring Boot connects to ActiveMQ through JMS: add the starter for ActiveMQ Classic or Artemis, configure the broker connection, send messages with a JMS client such as JmsTemplate, and receive them with @JmsListener. The design decisions that make the system dependable come next: choose a queue or topic based on who needs each message, set acknowledgement and transaction boundaries around the business work, and make consumers safe to retry.
How Spring Boot connects to ActiveMQ
Spring Boot supplies JMS infrastructure through broker-specific starters and configuration. Use the starter that matches the broker you intend to run; keep connection settings outside application code so they can vary between development, test, and production.
| Broker | Spring Boot starter | Configuration namespace | Mode noted by Spring Boot |
|---|---|---|---|
| ActiveMQ Classic | spring-boot-starter-activemq |
spring.activemq.* |
Not stated here |
| ActiveMQ Artemis | spring-boot-starter-artemis |
spring.artemis.* |
Explicit embedded or native mode |
Artemis embedded mode can suit local development or a tightly packaged deployment. Native mode connects the application to a broker that is already running. Choose deliberately: embedded operation ties broker lifecycle to the application, while native operation makes the broker a separately managed service.
Spring Boot documents JmsClient, JmsTemplate, JmsMessagingTemplate, and @JmsListener as JMS interfaces. Which ones are available and appropriate depends on the Spring Boot release in use. Match the Boot and broker-client release lines, especially where Jakarta package migration or pooling behavior matters.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- Better Ventilation for Your Equipment: This 1U rack shelf, with dimensions 17.6” x 10.0” (L x W) and 19.0” x 10.0” x 1.7” (L x W x H) including brackets, fits most network or wall-mounted racks, ensuring proper airflow to keep your equipment cool.
- Keeps Your Equipment Cool: The punch-out shelf bottom ensures optimal airflow, reducing heat buildup and improving ventilation. This helps prevent overheating, keeping your equipment cool and running efficiently.
- Durable and Long-Lasting Construction: Made from heavy-duty steel, this rack shelf offers exceptional durability. It provides reliable support, ensuring stability and strength, even in demanding environments like stages and studios.
- Easily Fits into Standard Racks: Compatible with all 19-inch server racks, this shelf integrates seamlessly into your existing setup. Whether wall-mounted or in a traditional rack, it provides a stable and secure foundation.
- Supports Heavy Loads: With a weight capacity of 110 lbs, this shelf is designed to support heavier equipment. It ensures your devices stay securely in place while providing stability and durability over time, even under heavy loads.
Send a message
A producer can inject JmsTemplate and send to an explicitly named destination:
@Service
class OrderPublisher {
private final JmsTemplate jmsTemplate;
OrderPublisher(JmsTemplate jmsTemplate) {
this.jmsTemplate = jmsTemplate;
}
void publish(OrderSubmitted event) {
jmsTemplate.convertAndSend("orders.submitted", event);
}
}This example illustrates the sending boundary, not a complete production event contract. The application must also decide how the event is serialized, which schema consumers expect, and how incompatible schema changes are handled.
Receive a message
A listener endpoint can be created by annotating a bean method with @JmsListener and naming its destination:
Rank #2
- Standard 1U Height: Get more space with our 1U server rack shelf—it comes in a set of 2! Perfect for 19-inch 4-post server racks, it's ideal for stacking routers, switches, firewalls, and other network gear. Easy storage and a neat setup in one simple solution!
- Heavy-Duty Construction: Crafted from premium Q235 carbon steel with a robust 0.06" (1.5 mm) thickness, our server rack shelf can handle up to 50 lbs (22.68 kg) with ease. Say goodbye to wobbles and tilts—perfect for keeping everything in its place!
- Optimal Ventilation: Featuring a perforated bottom design, our network rack shelf effectively reduces equipment temperature, ensuring stable operation and lowering the risk of malfunctions. Keep your gear running smoothly for longer-lasting, reliable performance.
- Flexible Partitioning: With each shelf offering a depth of 10 inches (254 mm), our rack mount shelf helps you organize and optimize your rack space efficiently. Keep your equipment neatly separated to reduce clutter and minimize interference or collisions.
- Installation Made Easy: Comes with all the screws and nuts you need—just grab a Phillips screwdriver and you're all set! Installation is a breeze, and you'll be up and running in no time. Enjoy a more efficient, streamlined setup!
@Component
class OrderHandler {
@JmsListener(destination = "orders.submitted")
void handle(OrderSubmitted event) {
// Validate, apply the business change, and record completion safely.
}
}Spring Boot documents that, when JMS infrastructure is present, a bean can be annotated with @JmsListener to create a listener endpoint. The destination name alone does not define ownership or behavior: document which service publishes it, which service consumes it, the event schema, ordering expectations, and retry or failure policy.
Choose a queue or topic based on delivery ownership
A queue is for point-to-point work distribution: a message is delivered to one consumer, and it is removed after acknowledgement. A topic is for publish-subscribe fan-out: each subscription receives a copy. A durable topic subscription retains messages while its subscriber is disconnected, until they are consumed.
| Question | Queue | Topic |
|---|---|---|
| Who should receive an event? | One consumer handles each message; multiple consumers can compete for work. | Each subscription gets its own copy, so multiple interested services can react independently. |
| What happens to a disconnected consumer? | Queue behavior depends on acknowledgement and broker storage configuration. | A durable subscription retains messages while disconnected; non-durable subscriptions do not provide that retention. |
| When does a message leave? | After acknowledgement, according to the queue delivery semantics. | Each subscription tracks its own delivery and consumption; one subscriber’s progress does not replace another’s. |
| Typical fit | Task distribution where one worker should perform a unit of work. | Notifications or domain events with several independent subscribers. |
Do not choose a topic merely because a message is called an event. If exactly one service should own and process each work item, a queue is the clearer model. If independent services need their own copy, use topic subscriptions and decide whether each subscriber needs durable retention while offline.
Rank #3
- KEEP YOUR DEVICES ORGANIZED: This 1U rack shelf is a perfect solution for organizing and securely holding your equipment. Whether you need a small shelf for compact setups or a large shelf for heavier devices, it’s designed to meet your needs.
- VERSATILE INSTALLATION OPTIONS: Built for both professional and home use, this rack mount shelf fits into metal wall shelves, rack mounts, and server racks, making it ideal for studios, offices, or server rooms.
- STRONG & RELIABLE SUPPORT: With a weight capacity of 110 lbs, this shelf rack can securely hold a variety of devices, from server accessories to computer racks & cabinets, ensuring stability and peace of mind.
- PROMOTES DEVICE LONGEVITY: The vented design ensures proper airflow to keep devices cool, making it ideal for items like rack mount UPS and other temperature-sensitive electronics.
- UNIVERSAL SIZE FOR EASY FIT: Compatible with all standard 19-inch racks, this shelf is perfect for small server racks, server rack shelves, and even custom setups like origami shelves, providing flexibility for different applications.
Design reliability around acknowledgement, retries, and side effects
Reliability is a policy made from several interacting choices, not a single broker switch. Acknowledgement timing determines when the broker considers delivery complete; redelivery determines what happens after an unsuccessful attempt; transactions can group messaging work; and durable broker storage affects what survives broker failure. Artemis documentation describes reliable delivery, local and XA transactions, and durable versus non-durable messages. The actual result depends on how the application and broker are configured together.
Make the business effect safe to repeat
A consumer can complete a business action and then fail before its acknowledgement reaches the broker. The message may be delivered again even though the first attempt changed application state. Design handlers to tolerate this: give each event a stable identifier, record processed identifiers or enforce a business uniqueness constraint, and make repeated handling produce the same intended outcome rather than duplicate charges, records, or notifications.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Place transaction boundaries where they protect useful work
Decide what must succeed together. If a consumer updates a database and acknowledges a JMS message in separate transactions, a crash between those operations can produce either repeated work or a lost opportunity to retry. A transaction that covers messaging and another resource may require XA support and adds operational complexity. Where a shared transaction is not practical, use an idempotent consumer and a durable record of processing or an outbox-style producer pattern so state changes and event publication can be reconciled.
Rank #4
- Compatible to: This Mounting Bracket is designed for the TAA compliant Universal VESA LCD Monitor in 19-inch network cabinet or server rack.
- Sturdy Structure: The LCD mounting bracket is made of cold rolled steel and supports 100mm & 75mm VESA mounted LCD panels.
- Adjustable Depth: This adjustable depth design enables an LCD panel to be mounted into the AV rack cabinet at various depths; allowing the rack or cabinet door to be closed.
- Multi-use: Besides using in 19" network cabinet or server rack, the LCD monitor can be mounted onto wall by adding this bracket onto a wall mount bracket or rack.
Set a bounded retry and failure-handling policy rather than allowing a permanently failing message to loop without visibility. Define which failures are transient, which require correction or operator action, and how the team can inspect and recover failed work. The exact redelivery and dead-letter configuration is broker- and version-specific, so verify it for the chosen release.
Persistence is not the same as end-to-end exactly-once processing
Durable broker storage or a durable subscription can preserve messages under the conditions supported by the broker configuration. It cannot by itself make an external database update, payment call, or email send happen exactly once. The consumer’s transaction boundary, acknowledgement timing, retry behavior, and idempotency strategy determine how those side effects behave after interruption.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose a protocol for the clients you need to connect
JMS and Jakarta Messaging standardize a Java programming API; they do not define a network wire protocol. Artemis supports Core, OpenWire, AMQP, MQTT, and STOMP. That distinction matters when a system includes non-Java services: sharing a JMS API does not make another language’s client wire-compatible by itself.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsBest Value
- Heavy Duty 1U Server Rack Shelf: Made from 1.5mm thick cold rolled steel with reinforced edges for superior strength. This 19-inch lenth 14-inch rack mount cantilever shelf supports up to 110 lbs (50 kg), ideal for servers, switches, routers, UPS units, and AV equipment
- Universal 19-Inch Rack Mount Compatibility: Designed to fit standard 19" server racks, network racks, and rack cabinets. Compatible with most 2-post and 4-post rack enclosures for flexible installation
- Ventilated Rack Shelf for Improved Airflow: Bottom and side ventilation slots promote airflow and heat dissipation inside your server rack cabinet to help prevent overheating of networking equipment
- Twist-Lock Anti-Slip Stoppers: Includes removable anti-slip stoppers that securely lock into place, helping prevent equipment from sliding off the shelf during operation or maintenance
- Convenient Cable Management: Includes reusable Velcro cable ties for clean cable management inside your network rack enclosure
| Need | Decision to make |
|---|---|
| Java services using Spring JMS | Select a broker-compatible JMS client and configure the broker’s supported transport for that client. |
| Clients in different languages | Choose a broker-supported protocol those clients can implement, then verify the exact client and broker versions interoperate. |
| Multiple protocol types | Confirm the required protocol is enabled and supported by the deployed Artemis version; test the real client combination rather than assuming JMS defines the wire format. |
Do not treat protocols as interchangeable labels. Client capabilities, authentication, destination mapping, transaction features, and message conversion can vary. Establish compatibility with a small integration test before committing a cross-language event contract.
Compare ActiveMQ Classic and Artemis against the deployment
The starter and configuration namespace are useful starting distinctions, but they do not answer every operational or migration question. The available documented differences are:
| Dimension | ActiveMQ Classic | ActiveMQ Artemis |
|---|---|---|
| Spring Boot starter | spring-boot-starter-activemq |
spring-boot-starter-artemis |
| Spring Boot configuration prefix | spring.activemq.* |
spring.artemis.* |
| Embedded versus separate broker mode | Not stated here | Spring Boot documents explicit embedded and native modes |
| Protocol support stated here | Not stated here | Core, OpenWire, AMQP, MQTT, and STOMP |
For persistence semantics, transaction requirements, operational tooling, client compatibility, and migration cost, evaluate the exact broker and Spring Boot versions rather than assuming parity from the JMS API. A migration can preserve Java-facing code while still changing configuration, transport, broker lifecycle, or operational procedures.
Configure for environments and verify the release combination
Keep broker-specific settings externalized and use the namespace matching the selected broker. For Artemis, choose embedded or native mode based on whether the application should host the broker or connect to a separately managed instance. Spring Boot also documents JMS caching through spring.jms.cache.* and optional pooled-JMS settings; validate pooling and caching choices against the selected release and workload rather than enabling them blindly.
Quick Recap
- Align versions. Select a Spring Boot release, its managed JMS client dependencies, and a compatible broker release. Check Jakarta package migration and protocol availability for that exact combination.
- Choose broker lifecycle. For Artemis, decide between embedded and native mode; provision and configure the broker accordingly.
- Externalize connection details. Set the correct
spring.activemq.*orspring.artemis.*properties outside source code, with environment-specific credentials and endpoints managed securely. - Define destinations and contracts. Name each queue or topic, document producer and consumer ownership, event schema, ordering assumptions, and retry behavior.
- Test failure paths. Verify a consumer crash before acknowledgement, redelivery after a transient error, duplicate delivery after a side effect, a disconnected durable subscriber, and broker restart behavior under the configured persistence policy.
- Check observability and recovery. Ensure the team can see consumer failures and backlog, identify repeatedly failing messages, and recover them without silently discarding business work.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
