As per the JMS specification, several headers, including JMSPriority, are set
on send() by the JMS provider (ActiveMQ). This means that values specified
by clients are overwritten.
Here's the spec; see section 3.4.11, How Message Header Values are Set:
Hi,
I try to run priority focussed tests with JMeter 2.11 against ActiveMQ 5.8
and some queues defined in the broker xml config.
I successfully managed to push messages into the queues by the
JMeter-Samplers JMS-Point-Point and also JMS-Publisher.
With both samplers I do set JMS properties
Is there a way in jmeter to set properties on the JMS producer? That might
work.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Testing-against-ActiveMQ-with-JMeter-how-to-set-JMSPriority-and-JMSExpiration-values-cannot-be-seen-r-tp4680960p4681003.html
Sent from the
Filed an issue and provided a patch:
https://issues.apache.org/bugzilla/show_bug.cgi?id=56510
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Testing-against-ActiveMQ-with-JMeter-how-to-set-JMSPriority-and-JMSExpiration-values-cannot-be-seen-r-tp4680960p4681048.html
Sent
I took a look at the jmeter source code, there are some other settings and
properties treated in a special way, e.g.:
1. Checkbox for persistent delivery -- set at the MessageProducer in
org.apache.jmeter.protocol.jms.client.Publisher
2. JMSCorrelationID taken from JMS-Properties list -- set at
Yes or to be correct at the message, e.g. CorrelationID:
org.apache.jmeter.protocol.jms.Utils.addJMSProperties(Message, MapString,
Object):
The same should apply to properties JMSPriority (msg.setJMSPriority(int))
and JMSExpiration (msg.setJMSExpiration(long)).
I will file a feature issue and
