DataSet Component
The DataSet component provides a mechanism to easily perform load & soak testing of your system. It works by allowing you to create DataSet instances both as a source of messages and as a way to assert that the data set is received.
URI format
dataset:name
Where name is used to find the DataSet instance in the Registry
Example
For example to test that 10 million messages are sent to a queue then consumed from a queue without loosing any messages.
// send the dataset to a queue
from("dataset:foo").to("activemq:SomeQueue");
// now lets test that the messages are consumed correctly
from("activemq:SomeQueue").to("dataset:foo");
The above would look in the Registry to find the foo DataSet instance which is used to create the messages.
Then you create a DataSet implementation, such as using the SimpleDataSet
Properties on SimpleDataSet
Property |
Description |
|---|---|
defaultBody |
Specifies the default message body. For SimpleDataSet it is a constant payload; though if you want to create custom payloads per message create your own derivation of DataSetSupport |
reportGroup |
Specifies the number of messages to be received before reporting progress. Useful for showing progress of a large load test |
size |
Specifies how many messages to send/consume |
Load testing ActiveMQ with Camel
There is an example of load testing an ActiveMQ queue using Camel in the ActiveMQ source code repository. The code lives at this location
You can grab the code
svn co https://svn.apache.org/repos/asf/activemq/trunk/activemq-camel-loadtest/
Then try running the test case
cd activemq-camel-loadtest mvn clean install
To see how the test is defined see the Spring XML file