Java Message Service (JMS) with ActiveMQ for Asynchronous Communication
Jul 31, 2025 am 01:14 AMJMS is the message communication API standard of the Java platform, supporting point-to-point and publish/subscribe models, and ActiveMQ is the message middleware it implements; 1. Start ActiveMQ service and listen to the default port; 2. Add activemq-client dependency in the Maven project; 3. Create producers to send messages to queues through ConnectionFactory; 4. Create consumers to receive messages asynchronously through MessageListener; this combination realizes system decoupling, traffic peak cutting, reliable delivery and asynchronous processing, which is suitable for traditional Java enterprise applications. Although there are more modern alternatives, they still have learning and use value.
In modern distributed systems, asynchronous communication is a key means to improve system decoupling, scalability and responsiveness. Java Message Service (JMS) combined with ActiveMQ is a classic combination of asynchronous messaging, especially suitable for enterprise-level Java applications.

What are JMS and ActiveMQ?
JMS is an API standard for sending and receiving messages in the Java platform, supporting two message models:
- Point-to-point (Queue) : The message is sent to the queue and a consumer processes a message.
- Publish/Subscribe (Topic) : The message is posted to a topic, and multiple subscribers can receive the same message.
ActiveMQ is an open source, JMS specification-based messaging middleware (message broker) developed by Apache. It supports multiple protocols (such as OpenWire, STOMP, MQTT) and can run across platforms, making it ideal for building loosely coupled asynchronous systems.

How to implement asynchronous communication using JMS ActiveMQ?
To use JMS to communicate asynchronously with ActiveMQ, the following steps are usually included:
1. Start ActiveMQ Service
First, download and start the service from the Apache ActiveMQ official website :

bin/activemq start
By default, ActiveMQ listens to tcp://localhost:61616
and provides a web console http://localhost:8161
.
2. Add Maven dependencies
In your Java project (such as using Maven), add the following dependencies:
<dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-client</artifactId> <version>5.17.3</version> </dependency>
3. Create a message producer (Producer)
The producer sends messages to a queue or topic:
import javax.jms.*; import org.apache.activemq.ActiveMQConnectionFactory; public class MessageProducer { private static final String BROKER_URL = "tcp://localhost:61616"; private static final String QUEUE_NAME = "example.queue"; public static void main(String[] args) throws JMSException { ConnectionFactory factory = new ActiveMQConnectionFactory(BROKER_URL); Connection connection = factory.createConnection(); connection.start(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); Destination destination = session.createQueue(QUEUE_NAME); MessageProducer producer = session.createProducer(destination); TextMessage message = session.createTextMessage("Hello from JMS Producer!"); producer.send(message); System.out.println("Sent message: " message.getText()); producer.close(); session.close(); connection.close(); } }
4. Create a message consumer
Consumers receive messages asynchronously, usually using MessageListener
to implement:
import javax.jms.*; import org.apache.activemq.ActiveMQConnectionFactory; public class MessageConsumer { public static void main(String[] args) throws JMSException { ConnectionFactory factory = new ActiveMQConnectionFactory(BROKER_URL); Connection connection = factory.createConnection(); connection.start(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); Destination destination = session.createQueue(QUEUE_NAME); MessageConsumer consumer = session.createConsumer(destination); consumer.setMessageListener(new MessageListener() { @Override public void onMessage(Message message) { if (message instanceof TextMessage) { try { System.out.println("Received: " ((TextMessage) message).getText()); } catch (JMSException e) { e.printStackTrace(); } } } }); // Keep the program running and wait for messages (may be in a more elegant way in actual applications) System.out.println("Waiting for messages..."); } }
Note: After the consumer uses
setMessageListener
, the message processing is asynchronous and will not block the main thread.
Usage scenarios and advantages
- System decoupling : Producers do not need to know the existence of consumers.
- Traffic peak cutting : In high concurrency scenarios, the message queue can buffer requests.
- Reliable delivery : ActiveMQ supports persistent messages to ensure that messages are not lost.
- Asynchronous processing : time-consuming operations such as sending emails and log processing can be placed in the queue for asynchronous execution.
Things to note
- Connection Management : It is recommended to use connection pools (such as
PooledConnectionFactory
) in production environments. - Transaction and confirmation mode : Select
Session.SESSION_TRANSACTED
or manually confirm according to reliability requirements. - Exception handling : When a network is interrupted or a consumer crash, the reconnection and retry mechanisms need to be reasonably configured.
- Persistent subscription : For the Topic model, if the consumer is offline, he/she can receive missed messages through a persistent subscription.
Basically that's it. JMS ActiveMQ is not the latest technology (now more modern options such as Kafka and RabbitMQ), but it is still widely used in traditional Java EE or Spring projects, especially suitable for scenarios that require standard JMS support. Mastering it is very helpful for understanding the principles of message middleware.
The above is the detailed content of Java Message Service (JMS) with ActiveMQ for Asynchronous Communication. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three main differences between Callable and Runnable in Java. First, the callable method can return the result, suitable for tasks that need to return values, such as Callable; while the run() method of Runnable has no return value, suitable for tasks that do not need to return, such as logging. Second, Callable allows to throw checked exceptions to facilitate error transmission; while Runnable must handle exceptions internally. Third, Runnable can be directly passed to Thread or ExecutorService, while Callable can only be submitted to ExecutorService and returns the Future object to

Java supports asynchronous programming including the use of CompletableFuture, responsive streams (such as ProjectReactor), and virtual threads in Java19. 1.CompletableFuture improves code readability and maintenance through chain calls, and supports task orchestration and exception handling; 2. ProjectReactor provides Mono and Flux types to implement responsive programming, with backpressure mechanism and rich operators; 3. Virtual threads reduce concurrency costs, are suitable for I/O-intensive tasks, and are lighter and easier to expand than traditional platform threads. Each method has applicable scenarios, and appropriate tools should be selected according to your needs and mixed models should be avoided to maintain simplicity

In Java, enums are suitable for representing fixed constant sets. Best practices include: 1. Use enum to represent fixed state or options to improve type safety and readability; 2. Add properties and methods to enums to enhance flexibility, such as defining fields, constructors, helper methods, etc.; 3. Use EnumMap and EnumSet to improve performance and type safety because they are more efficient based on arrays; 4. Avoid abuse of enums, such as dynamic values, frequent changes or complex logic scenarios, which should be replaced by other methods. Correct use of enum can improve code quality and reduce errors, but you need to pay attention to its applicable boundaries.

JavaNIO is a new IOAPI introduced by Java 1.4. 1) is aimed at buffers and channels, 2) contains Buffer, Channel and Selector core components, 3) supports non-blocking mode, and 4) handles concurrent connections more efficiently than traditional IO. Its advantages are reflected in: 1) Non-blocking IO reduces thread overhead, 2) Buffer improves data transmission efficiency, 3) Selector realizes multiplexing, and 4) Memory mapping speeds up file reading and writing. Note when using: 1) The flip/clear operation of the Buffer is easy to be confused, 2) Incomplete data needs to be processed manually without blocking, 3) Selector registration must be canceled in time, 4) NIO is not suitable for all scenarios.

Java's class loading mechanism is implemented through ClassLoader, and its core workflow is divided into three stages: loading, linking and initialization. During the loading phase, ClassLoader dynamically reads the bytecode of the class and creates Class objects; links include verifying the correctness of the class, allocating memory to static variables, and parsing symbol references; initialization performs static code blocks and static variable assignments. Class loading adopts the parent delegation model, and prioritizes the parent class loader to find classes, and try Bootstrap, Extension, and ApplicationClassLoader in turn to ensure that the core class library is safe and avoids duplicate loading. Developers can customize ClassLoader, such as URLClassL

Javaprovidesmultiplesynchronizationtoolsforthreadsafety.1.synchronizedblocksensuremutualexclusionbylockingmethodsorspecificcodesections.2.ReentrantLockoffersadvancedcontrol,includingtryLockandfairnesspolicies.3.Conditionvariablesallowthreadstowaitfor

The key to Java exception handling is to distinguish between checked and unchecked exceptions and use try-catch, finally and logging reasonably. 1. Checked exceptions such as IOException need to be forced to handle, which is suitable for expected external problems; 2. Unchecked exceptions such as NullPointerException are usually caused by program logic errors and are runtime errors; 3. When catching exceptions, they should be specific and clear to avoid general capture of Exception; 4. It is recommended to use try-with-resources to automatically close resources to reduce manual cleaning of code; 5. In exception handling, detailed information should be recorded in combination with log frameworks to facilitate later

HashMap implements key-value pair storage through hash tables in Java, and its core lies in quickly positioning data locations. 1. First use the hashCode() method of the key to generate a hash value and convert it into an array index through bit operations; 2. Different objects may generate the same hash value, resulting in conflicts. At this time, the node is mounted in the form of a linked list. After JDK8, the linked list is too long (default length 8) and it will be converted to a red and black tree to improve efficiency; 3. When using a custom class as a key, the equals() and hashCode() methods must be rewritten; 4. HashMap dynamically expands capacity. When the number of elements exceeds the capacity and multiplies by the load factor (default 0.75), expand and rehash; 5. HashMap is not thread-safe, and Concu should be used in multithreaded
