Bug 45571 - JMS Sampler Correlation Enhancement
Summary: JMS Sampler Correlation Enhancement
Status: RESOLVED FIXED
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-05 18:21 UTC by Timothy Rundle
Modified: 2008-10-02 12:26 UTC (History)
0 users


Attachments
correlation strategy implementation (6.82 KB, patch)
2008-08-05 18:21 UTC, Timothy Rundle 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Rundle 2008-08-05 18:21:41 UTC 
Created attachment 22392 [details]
correlation strategy implementation

JMS Correlation strategies involve more that just matching correlation ids.  I suggest adding a drop down when doing request/reply to choose of the following correlation strategies:

1) Request CorrelationId to Response CorrelationId
2) Request MessgaeId to Response MessgaeId
3) Request MessageId to Response CorrelationId


I have attached a patch file that implements these scenarios.  Also included in the patch are some changes to make working with WebSphereMQ easier.  For example WMQ doesn't allow the CorrelationId to be set via setStringProperty.  So in the addProperties method if the property name is JMSCorrelationID, the msg.setJMSCorrelationID is called.
Comment 1 Sebb 2008-10-02 12:26:41 UTC 
Thanks for the patch; applied to SVN in trunk:

URL: http://svn.apache.org/viewvc?rev=701218&view=rev
Log:
Bug 45571 - JMS Sampler correlation enhancement
Comment 2 The ASF infrastructure team 2022-09-24 20:37:42 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2142