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
Or if you really would rather be more explicit you can create the broker first using the following Java code
or you could use Spring Support.
If your application code is using JNDI to lookup the JMS
Destination's 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
EmbeddedActiveMQBroker JUnit Rule (ActiveMQ 5.13)
If your test code is using JUnit, then you could use the
EmbeddedActiveMQBroker JUnit Rule provided in the
activemq-junit library. Add the
activemq-junit library along with the
activemq-broker libraries for the version of ActiveMQ you want to test with. The rule will use whatever version of ActiveMQ it finds in the classpath, so the ActiveMQ libraries need to be specified if they are not already there.
If you are using Maven, add the following to your
Then add the
EmbeddedActiveMQBroker JUnit Rule to your test, and JUnit will start the embedded broker at the beginning of each test and stop the broker at the end of the test.
By default, the
EmbeddedActiveMQBroker will configure the broker as non-persistent, and the only transport available will be the VM transport. To customize this configuration, either extend the
EmbeddedActiveMQBroker class and override the
configure() method, or use an XML configuration for the broker.
EmbeddedActiveMQBrokerusing XML configuration, you may need to add additional libraries to the classpath to support XBean configuration of ActiveMQ.
Note that to use the XML configuration, you may need to add additional libraries on the classpath to support the XBean configuration of ActiveMQ. The versions of the
spring-context library should correspond with the version used by your selected version of ActiveMQ.
Then you can use the VM URI to connect with the broker
You can also get a connection factory from the