Usually you don't want to do that. Threads make your test much more complicated, and you must take into account timing, locking and synchronization issues that can make things very unpredictable. In the vast majority of cases where someone is attempting to use threads, there is no reason to. If your test has the same user doing things one after another and you're trying to use threads to do this, rewrite your test to be linear.
If you really must use threads after all that discouraging, I wrote a small plugin that enables passing data between threads. There are probably more intuitive ways it could work, but it worked for what I needed it to. You can find it at https://github.com/FlyingRhenquest/JmeterThreadGlobal. You might also want to look at my thread synchronization plugin, which I like slightly more than the stock jmeter thread synchronization time. https://github.com/FlyingRhenquest/JmeterThreadSync. -- Bruce Ide [email protected]
