jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Divyang Raval <>
Subject Re: Passing the JDBC query values list from one thread group to another
Date Mon, 06 Jan 2020 07:22:39 GMT
Hi Soumya,

It can be achieved in 2 steps.

Add Regx extractor on JDBC query response to extract target field.
While extracting list of values you can set Match No.= -1.
Let's say variable name in Regx extractor is "listdata".

Step-2 : Add For each controller in test plan and give input variable=
And output variable let's say "data".
Check the check box of add _.

Under this controller add your next request where you want to iterate based
on JDBC output you recieved and use ${data} to achieve the target.

Feel free to let me know if you find any difficulty while execution.


On Mon, Jan 6, 2020, 12:33 PM Soumya Nayak <> wrote:

> Hi Team,
> I have a set up thread group where I am running a JDBC request to get some
> "n" no of row data into 4 variables.
> Now I want to access all the above variable values in a loop(for n DB
> records) in another thread group. How can I achieve this?
> For a single variable value access I was able to achieve by defining a
> bean shell assertion and setting the variable as a property
> (${__setProperty()) and accessing the property({__property()} in another
> thread group.  But , how to achieve the same when we have a list of values
> fetched from JDBC request in one thread group and access all the list
> another thread group ?
> Regards,
> Soumya
> ******************************************************************************************
> This message may contain confidential or proprietary information intended
> only for the use of the
> addressee(s) named above or may contain information that is legally
> privileged. If you are
> not the intended addressee, or the person responsible for delivering it to
> the intended addressee,
> you are hereby notified that reading, disseminating, distributing or
> copying this message is strictly
> prohibited. If you have received this message by mistake, please
> immediately notify us by
> replying to the message and delete the original message and any copies
> immediately thereafter.
> If you received this email as a commercial message and would like to opt
> out of future commercial
> messages, please let us know and we will remove you from our distribution
> list.
> Thank you.~
> ******************************************************************************************

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message