How do I pass a variable from one Thread Group to another in JMeter

According to JMeter documentation:

16.12 Sharing variables between threads and thread groups

Variables are local to a thread a variable set in one thread cannot be read in another. This is by design. For variables that can be determined before a test starts, see Parameterising Tests (above). If the value is not known until the test starts, there are various options:

1. Store the variable as a property - properties are global to the JMeter instance
2. Write variables to a file and re-read them.
3. Use the bsh.shared namespace - see 16.8.2 Sharing Variables
4. Write your own Java classes

Another way to pass variable between the threads is to use jmeter-plugins as mentioned by Andrey Botalov below.

But I found that it is a bit confusing to use it first time but it gives full control of variable during passing from thread to thread. Follow my example with BeanShell usage and you see how easy it is:

Next referring to sections in picture bellow:

(1.1) Here I created custom variable in User Defined Variables (or you can do it with BSF Proccessor - disabled in this example (1.2))

(2.1)(2.4)I successfully used variable in first thread - nothing special :)

(2.2)Added BeanShell PostProcessor and customized my variable

(2.3)Added it to queue

(3.1) In second thread - variable is taken from queue - with any name you want. But be careful, use wisely Timeout, because this thread will wait til previous finish so it can get modified variable (experiment with some long response)

(3.2)(3.3)(3,4)That repeated steps of using and modifying variable

(3.5) Variable is sent once again in new queue - so provide new name to it

(4.1)(4.2)(4.3) Grabbed modified variable from new queue works like charm

Warning

1. If you add more threads then add some Counter to Thread Group with variable and add this variable name to queue name - do the same in Thread Group where you try to catch queue so queue will have unique name for each thread (write a comment if you need some clearer explenation)

2. If you have more than one http Request in one Thread Group then add thread communication pre processor as a child of last (or other if you want to achieve some custom thing) http Request

Play, modify, customize to get best result :) Adding more threads can result in unwanted behavior so you need to be watchful.

I was not able to do this with variables (since those are local to individual threads). However, I was able to solve this problem with properties!

Again, my first ThreadGroup does all of the set up, and I need some information from that work to be available to each of the threads in the second ThreadGroup. I have a BeanShell Assertion in the first ThreadGroup with the following:

${__setProperty(storeid, ${storeid})};

The ${storeid} was extracted with an XPath Extractor. The BeanShell Assertion does other stuff, like checking that storeid was returned from the previous call, etc.

Anyway, in the second ThreadGroup, I can use the value of the "storeid" property in Samplers with the following:

${__property(storeid)}

Works like a charm!

I found which I believe is the most simple way to get this done.

Use

Bean Shell PostProcessor

Set in one Thread Group

to set the variable (http://jmeter.apache.org/usermanual/best-practices.html#bsh_variables)

import org.apache.jmeter.util.JMeterUtils;
JMeterUtils.setProperty("PC_CREATED_PROMO_CODE", "value");

OR if you want to set it to a value contained in another variable

import org.apache.jmeter.util.JMeterUtils;
JMeterUtils.setProperty("PC_CREATED_PROMO_CODE", vars.get("Extracted_PC_CREATED_PROMO_CODE"));

Get in the other Thread Group

And then from the other thread group, read it via (http://jmeter.apache.org/usermanual/functions.html#__property)

${__property(PC_CREATED_PROMO_CODE)}

JMeter Plugins has Inter-Thread Communication for this purpose.

There are 2 methods to use it:

• PostProcessor/PreProcessor
• Functions __fifoPut and __fifoPop

In my opinion PostProcessor/PreProcessor is easier to use.