activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Mielke (JIRA)" <>
Subject [jira] [Created] (AMQ-3280) Add support for message selectors and message headers in maven-activemq-perf-plugin.
Date Tue, 12 Apr 2011 10:10:05 GMT
Add support for message selectors and message headers in maven-activemq-perf-plugin.

                 Key: AMQ-3280
             Project: ActiveMQ
          Issue Type: New Feature
          Components: Performance Test
    Affects Versions: 5.5.0
         Environment: maven-activemq-perf-plugin, message selectors
            Reporter: Torsten Mielke
         Attachments: AMQ-3280.patch

The maven ActiveMQ performance plugin can be used as a general test framework. 
It currently lacks support for specifying message selectors in the consumer. 
I request this support to be added and attach a possible implementation. 

In this implementation, the consumer additionally supports the following configuration option:
-Dconsumer.messageSelector="MyHeader = 'MyValue' AND JMSType = 'car'"

You can specify message selector criterias, as explained in
However this implementation only supports header based criterias. 

In order to produce messages that match the message selector of the consumer it is necessary
to also extend the producer to support message headers. 
On the producer side message headers can be specified using this arguments

whereby each header follows the syntax name=value and multiple headers can be separated using
':' on the same line. 
There can only be one occurrence of -Dproducer.header. If multiple are specified, they will
override each other. 
Hence multiple headers need to be separated by ':'

The sample message header configuration of the producer above will match the message selector
configuration of the consumer above.

If this patch gets accepted, the documentation of the [maven-activemq-perf-plugin|]
needs to be updated as well. 

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message