You might be able to coerce a synchronizing timer into doing what you want. If that doesn't work for you, you might have to go off and write your own sampler to communicate data between the threads. It's easy enough to create a config data element and bind an actual java object to a jmeter variable. That allows you to do anything Java can do in your test.
I did some thread sync and communication stuff over on github ( https://github.com/flyingrhenquest). Works all-right, makes the test very hard for other testers to understand and maintain. So feel free to browse around in there for ideas or use my plugins or both, but keep in mind that it's probably a bad idea from a testing perspective. I guess this is kind of like giving you a foot-shooting gun and explaining that shooting yourself in the foot is a bad idea heh heh heh. -- Bruce Ide [email protected]
