When unit testing code with JMS you'll typically want to avoid the overhead of running separate proceses; plus you'll want to increase startup time as fast as possible as you tend to run unit tests often and want immediate feedback. Also persistence can often cause problems - as previous test case results can adversely affect future test case runs - so you often need to purge queues on startup.

So when unit testing JMS code we recommend the following

  • Use an embedded broker to avoid a separate broker process being required
  • Disable broker persistence so that no queue purging is required before/after tests
  • It's often simpler and faster to just use Java code to create the broker via an XML configuration file using Spring etc.

You can do all of this using the following Java code to create your JMS ConnectionFactory which will also automatically create an embedded broker

For more configuration options see the VM Transport Reference and the Broker Configuration URI

Or if you really would rather be more explicit you can create the broker first using the following Java code

or you could use the Spring Support

Using JNDI

If your application code is using JNDI to lookup the JMS ConnectionFactory and Destinations to use, then you could use the JNDI Support in ActiveMQ.

Add the following jndi.properties to your classpath (e.g. in src/test/resources if you are using maven).

You should then consider using Dynamic destinations in JNDI so that your code looks up destinations via

To avoid having to explicitly configure every single JMS destination in the jndi.properties file, please see the other options for creating destinations.

© 2004-2011 The Apache Software Foundation.
Apache ActiveMQ, ActiveMQ, Apache, the Apache feather logo, and the Apache ActiveMQ project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram