Playing with ActiveMQ using Maven

In this post I demonstrate how to get started with ActiveMQ. This is very much a simple beginners guide, and shows you just enough to get a message traveling between 2 separate applications.

I’ve separated the example up into 3 sections. The ‘producer’ section will create test messages on a queue, the ‘consumer’ will consume them, and the final section, ‘mq’, will host the ActiveMQ instance. It would be possible to do this in a single application using an embedded broker, however I think it’s useful to demonstrate them separately, as potentially the components could be on separate machines.

To get started, let’s create the 3 projects:

Setting up ActiveMQ

We’ll get the ActiveMQ broker up and running first. Change directory into 'mq' and modify the pom.xml file as below:

We now need to create a configuration file for ActiveMQ, which will reside in conf/activemq.xml. Below you can see a very minimal config which will be sufficient for our needs.

That’s all we need! We can now launch ActiveMQ by simply running the following:

Creating the Producer

We need to modify the pom.xml for the producer to include the JMS and ActiveMQ dependencies. I’ve also added the jboss repository so that JMS will download automatically without needing to manually install it into your local maven repository.

I’ve decided to separate the Producer app into 2 files. There’s the App class, and the Producer class. The App class creates the ConnectionFactory, which is the only ActiveMQ specific bit of code, passes it to the constructor of the Producer class, calls the run method, and finally the close method.

This application can be run by executing the following:

The Consumer

The consumer is pretty simple, and not that different from the producer. This class implements the MessageListener interface, causing the onMessage method to be called everytime a message is queued in the ‘test’ queue.

Assuming you’re run the producer at least once, you should have messages on your queue ready to consume. When you run the consumer you will see a flood of messages.

This process will not terminate, and will sit there waiting forever for messages – press CTRL-C to terminate.

To learn more about messaging, I strongly advise Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions.

Useful links

20 thoughts on “Playing with ActiveMQ using Maven”

  1. In a previous post, “Playing with ActiveMQ using Maven”, I showed how to produce and consume simple messages using Java. In this short post I show how to access these messages from PHP using STOMP. Assuming you are continuing from my previous a

  2. Really Sir, suberb.

    Just I copy and past code in my application and got running without changing a single line code. I only create one project and put, and


    Binod Suman

  3. thanks for this tutorial – i just played around with RabbitMQ and wanted to take a quick look at ActiveMQ and this is the article I’ve searched for πŸ™‚

  4. I tried runing this tutorial. When I tried consumer, i do not see any messages. Also, the consumer process terminates nicely ( as opposed to the acertion “will not terminate” in the tutorial ). Any suggestion as to what might have gone wrong ?. As such I did not receive any errors during bulding 3 projects.

    1. Sorry, I figured out the problem myself. My modified source code App were in a different directory. Thank you for an excellent tutorial. This is one of the finest I have seen so far.

  5. hi. it is really great post.

    i copied and past the codes. getting error like this :

    [ERROR] Failed to execute goal org.apache.activemq.tooling:maven-activemq-plugin:5.2.0:run (default-cli) on project jal-mq: Failed to start Activ
    eMQ Broker: Illegal character in opaque part at index 5: file: ./activemq.xml -> [Help 1]
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.activemq.tooling:maven-activemq-plugin:5.2.0:run (defau
    lt-cli) on project jal-mq: Failed to start ActiveMQ Broker
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(
    at org.apache.maven.DefaultMaven.doExecute(
    at org.apache.maven.DefaultMaven.execute(
    at org.apache.maven.cli.MavenCli.execute(
    at org.apache.maven.cli.MavenCli.doMain(
    at org.apache.maven.cli.MavenCli.main(
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(
    Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to start ActiveMQ Broker
    at org.apache.activemq.maven.BrokerMojo.execute(
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
    … 19 more
    Caused by: Illegal character in opaque part at index 5: file: ./activemq.xml
    at org.apache.activemq.maven.BrokerMojo.execute(
    … 21 more

  6. Very nice tutorial. Only one little hitch on the way (like javax.jms not found in the repository as shown in your example). And also you split the code for producer into two classes and the label for the second code listing is copy-paste from the first listing. tiniest little bit misleading. These are just ideas for improvement. Loved the simple way you constructed this example, now i can play with jms stuff πŸ™‚ thanks

  7. Pingback: ActiveMQ and Maven
  8. If you get a compile error on the consumer, add the javax.jms and activemq dependencies, and the jboss repository to the consumer pom file.

Leave a Reply

Your email address will not be published. Required fields are marked *