DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=44144>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44144 ------- Additional Comments From [EMAIL PROTECTED] 2007-12-27 06:41 ------- Actually, after a bit more investigation, I think keying on JMSCorrelationID would be a better idea for the FixedQueueExecutor and the Receiver. Although, in principle, keying on JMSMessageID should be ok, I've been running some tests with ActiveMQ 4.1.1 and I can see that whenever ActiveMQ sends a message, it sets a new JMSMessageID, even if you've written a MessagePostProcessor to reset/preserve the message id. The situation I am seeing fail is: a) JMeter sends a message to queue A with message id 1 b) My code reads message id 1 from queue A, does some processing and compiles a brand new message. c) My code puts the new message on queue B, and a MessagePostProcessor attempts to set the JMSMessageID to 1. d) ActiveMQ goes ahead and assigns a new message id just before sending. e) JMeter reads from queue B. Its expects message id 1, but thanks to ActiveMQ, it finds message id ?. Failure! A quick retry with a recompiled FixedQueueExecutor and Receiver that key on JMSCorrelationID succeeds if I re-run the above test. This makes more sense as section 3.4.5 of the JMS 1.1 spec states: "A client can use the JMSCorrelationID header field to link one message with another. A typical use is to link a response message with its request message." With this in mind, I think the proposed fix should be to change org.apache.jmeter.protocol.jms.sampler.FixedQueueExecutor to key the sent message in to the MessageAdmin object using JMSCorrelationID. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
