| Summary: | jms receiver will not validate if JMSCorrelationID is not populated | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | Richard Donovan <rdonovan2005> |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | cafed00d, tony.lbvre |
| Priority: | P2 | ||
| Version: | 2.3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: |
svn diff of Receiver.java with modified JMS request ID
JMS request response sampler log JMS request response sampler log for nightly build |
||
|
Description
Richard Donovan
2008-11-03 12:47:48 UTC
Thanks, fixed in SVN: URL: http://svn.apache.org/viewvc?rev=711364&view=rev Log: Bug 46142 - JMS Receiver now uses MessageID Please back out this change as it causes OpenMQ to fail. When resending jms messages there seems to be no requirement to retain the message id. The correlation id is designed to do exactly what JMeter requires - all the client has to do is populate it which is not done automatically. *** Bug 47288 has been marked as a duplicate of this bug. *** +1, yes, please back out this change. The JMS provider implementations compute itself the JMSMessageID (as does TIBCO EMS) and the client doesn't have control over it. "The JMSMessageID header field contains a value that uniquely identifies each message sent by a provider. When a message is sent, JMSMessageID is ignored. When the send method returns, the field contains a provider-assigned value." source: Java™ Message Service Version 1.1 April 12, 2002 3.4.3 JMSMessageID Using JMSMessageID has a correlation ID may be only useful for testing the EMS server itself. Created attachment 25603 [details]
JMS request response sampler log
Log showing that JMS request response support is not working as expected in TIBCO EMS in jmeter 2.4.3
The application being tested uses the request messageID to set the response correlationID
Created attachment 25604 [details]
JMS request response sampler log for nightly build
JMS Point-to-Point correlation is now selectable; can choose to match the request MessageId or Correlation Id against the response MessageId or CorrelationID. Hopefully that will satisfy all possible JMS application requirements. URL: http://svn.apache.org/viewvc?rev=955958&view=rev Log: Bug 46142 - JMS Point-to-Point correlation problems Modified: jakarta/jmeter/trunk/docs/images/screenshots/jms/JMS_Point-to-Point.png jakarta/jmeter/trunk/src/core/org/apache/jmeter/resources/messages.properties jakarta/jmeter/trunk/src/protocol/jms/org/apache/jmeter/protocol/jms/control/gui/JMSSamplerGui.java jakarta/jmeter/trunk/src/protocol/jms/org/apache/jmeter/protocol/jms/sampler/JMSSampler.java jakarta/jmeter/trunk/xdocs/changes.xml jakarta/jmeter/trunk/xdocs/images/screenshots/jms/JMS_Point-to-Point.png jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml The fixes are in nightlies from r955958. Please test and report any problems ASAP. Without great testing this is working for me now (Tibco JMS using request messageId as correlationId in reply) (In reply to comment #8) > The fixes are in nightlies from r955958. > > Please test and report any problems ASAP. If you interested in implementing some unit test code, you could use mockrunner... I tried but there are some minor problems in the JNDI support (Context.getEnvironment() throws NotImplementedException )and in the credentials code of jmeter. Just a sugestion... OK, thanks for confirming that Tibco is working OK. Given that the previous behaviour can still be selected by suitable choice of the options, I'm closing this bug. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2171 |