[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jmeter-dev
Subject:    DO NOT REPLY [Bug 6597]  -
From:       bugzilla () apache ! org
Date:       2002-04-23 23:18:00
[Download RAW message or body]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6597>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6597

start/stop test indication





------- Additional Comments From dim@bigpond.net.au  2002-04-23 23:17 -------
I have just attached a patch for this that does the following:
   * In ThreadGroup, add a threadStopped() that keeps track of which threads 
have stopped.  When there are zero threads left, this method calls 
ThreadGroup.SampleQueue.stop(), which causes the thread in SampleQueue to exit.
   * In JMeterThread, when the run() method finishes, call group.threadStopped
() to indicate the thread has finished.

There is also a patch for nongui.bat to make it work.

Note that this patch assumes that each JMeterThread object is run once and only 
once.  At the moment ThreadGroup.threadCount() that is responsible for counting 
the number of threads in a group, is called in the JMeterThread constructor.  
Perhaps this would be better at the start of the run() method.  There is also 
the possibility of moving the group.threadStopped() call to a finally block in 
the run method.

I've only just started looking at the code so have done the bare minimum for 
now.

--
To unsubscribe, e-mail:   <mailto:jmeter-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jmeter-dev-help@jakarta.apache.org>

[prev in list] [next in list] [prev in thread] [next in thread]