Välkommen till Callista Enterprise blogg - här finns tekniska artiklar, presentationer och nyheter om arkitektur och systemutveckling. Håll dig uppdaterad genom att följa oss på Twitter.
Callista Enterprise medarbetare Johannes Carlén

Lightweight messaging development using Active MQ

// Johannes Carlén

This is a guide to setting up a lightweight messaging development environment with Active MQ using Tomcat as the application server. This tips might be of help to you regardless you are using another platform such as Websphere MQ or just want to try out JMS in your web or Java application.

When integrating enterprise applications and services, Websphere MQ as messaging backbone is a common choice. While Websphere MQ is a valid, stable platform for production environments, the same platform makes a large, clumsy footprint in the development environment, making testing of services almost impossible in a sensible way. This is totally the opposite way of agile development methods where unit testing and test automation plays an important role. A quite easy way to help you out is to replace WMQ in your development environment with a more lightweight alternative /platform such as Active MQ /Spring / Tomcat.

Design wise there are three main different scenarios to think about.

  1. You are the service
  2. You are the caller making an asynchronous call
  3. You are the caller making a synchronous call (Request-Reply)

We begin with a look at the first scenario, where we need to be able to accept and read messages. Then we move on to act as the caller, the sender of these messages. I will not cover the third scenario in this post, why I will explain later.

First of all - download Tomcat, ActiveMQ, and Spring, create a web project and place the jars in the lib folder of your web app. Or you can just download the zip file containing the example code at the end of this page

Implementing the Jms listener

There are several ways of implementing a Jms Listener and I will show you one way. There are four main artifacts needed to make this possible.

  • A Jms listener implementation class that receives the call
  • A Spring configuration declaring the listener bean, the factory and destinations
  • We need to declare resources in the Tomcat context
  • We also have to bind the resources in the web.xml

Jms Listener:

public class MyService implements MessageListener {
  public void onMessage(Message msg) {
    if (msg instanceof TextMessage) {
      try {
        String text = ((TextMessage) msg).getText();
      } catch (JMSException e) {

In the spring context we need to create the queue connection factory and a destination that maps to the physical queue:

<bean id="jmsQueueConnectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
  <property name="jndiTemplate"><ref bean="jndiTemplate" /></property>
  <property name="jndiName"><value>jms/cf</value></property>
  <property name="resourceRef"><value>true</value></property>
<bean id="myDestination" class="org.springframework.jndi.JndiObjectFactoryBean">
  <property name="jndiTemplate"><ref bean="jndiTemplate" /></property>
  <property name="jndiName"><value>jms/myQueue</value></property>
  <property name="resourceRef"><value>true</value></property>

as well as a listener container in which we inject the listener

<bean id="myContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer">
  <property name="connectionFactory" ref="jmsQueueConnectionFactory" />
  <property name="messageListener" ref=" myServiceBean" />
  <property name="concurrentConsumers" value="5" />
  <property name="destination" ref="myDestination" />
<bean id="myServiceBean" class="se.callistaenterprise.MyService" />

Then we need to let Tomcat be aware of the messaging server. It is possible to embed the ActiveMQ instance in the same JVM as Tomcat, but I have chosen to let ActiveMQ startup as a standalone server to make this environment resemble a normal setup as much as possible. If you are running Windows, ActiveMQ comes with a handy possibility to create a Windows service. There is also a practical reason for keeping ActiveMQ separate - it takes about ten seconds for ActiveMQ to start which makes it quite cumbersome when you need to restart yor Tomcat now and then.

In the Tomcat context of your application, make a reference to a connection factory as well as to the specific queue:

<?xml version="1.0" encoding="UTF-8"?>
  <Resource name="jms/cf" auth="Container"
      description="JMS Connection Factory"
      brokerURL="tcp://localhost:61616" brokerName="LocalActiveMQBroker"
      useEmbeddedBroker="false" />

  <Resource name="jms/myService" auth="Container"
      physicalName="MY.SERVICE" />

One thing that is nice about Tomcat is that you can place this context information in a file named context.xml in the META-INF folder of your web application and Tomcat just reads it from there. No need to fiddle in the config folders.

The last thing we need is to map the resources in web.xml and kickstart the Spring context initialization:


This is all to it, just deploy and run ActiveMQ and Tomcat. Since ActiveMQ creates the queue on the fly we don’t have to care about doing that by hand. There is an admin gui in ActiveMQ that lets you send simple text messages. Just go to http://localhost:8161/admin and try your new service.

Making an asynchronous call

The second scenario is to call our remote service asynchronously through the messaging platform. I am using the Spring JmsTemplate to send messages so we need to add this to our config file as well as the bean that uses it:

<bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
  <property name="connectionFactory"><ref bean="jmsQueueConnectionFactory" />
  <property name="receiveTimeout" value="20" />
<bean id="caller" class="se.callistaenterprise.JmsService">
  <property name="jmsTemplate" ref="jmsTemplate" />
  <property name="destination" ref="myDestination" />

The Java code of the caller bean:

public void sendMessage(final String messageText) throws JMSException {
  jmsTemplate.send(destination, new MessageCreator() {
    public Message createMessage(Session session) throws JMSException {
      TextMessage message = session.createTextMessage(messageText);
      return message;

In order to test this, create a servlet which could contain code like this:

Caller producer = (Caller) WebApplicationContextUtils.
try {
  String message = "A Callista Enterprise message";
} catch (JMSException e) {

And there you go!

The third scenario - the Request-Reply pattern - is something I may address in a later post. The Spring JmsTemplate currently lacks (as of version 2.5.4) a proper way of handling the correlation id (used for identifying the reply) that is extracted from the sent message. This pattern, though, is supposed to be addressed in the next version.


Tack för att du läser Callista Enterprise blogg.
Hjälp oss att nå ut med information genom att dela nyheter och artiklar i ditt nätverk.