Hi Michael, Thanks for answering. Why shouldn't I use JMeterContextService.getNumberOfThreads()? When I place it under the rampUpDelay() it works perfect. Do you have any idea how to get the number of running threads from the remote machine? Thanks.
On 6/14/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > there is a function __threadNum which is certainly not exactly what you > want, but it might provide enough to meet your needs. You can put this > function in the name of a sampler, for instance, and by doing so, the > thread number will appear in the aggregate listener, for example. > > What is needed is to incorporate number of running threads into > sampleresults so that listeners can use the number for > graphing/calculations. What you are seeing is that the client machine > doesn't know how many threads are running on the remote machine. > > -Mike > > On Tue, 2005-06-14 at 16:23 +0300, Yuval wrote: > > Hi, > > I'm trying to add a label to one of the listeners which will display the > > number of running threads. > > Since I need the number of active threads (and JMeter is spawning all > the > > threads at the beginning of the test) I moved the > > JMeterContextService.incrNumberOfThreads() after the rampUpDelay(). > > This way I can see the number of active threads. > > My problem is that everything works fine when everything is working on > the > > same machine. But when I use the jmeter-server the > > JMeterContextService.incrNumberOfThreads() always returns 0 . > > Any ideas how to solve this issue? > > Thanks, > > Y. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
