You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2005/09/13 16:08:18 UTC
DO NOT REPLY [Bug 36619] -
Thread group Stop Test doesn't work with Loop count forever
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36619>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36619
philip.thatcher@anite.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From philip.thatcher@anite.com 2005-09-13 16:08 -------
Hmmmmm. There's more to this. It all works fine with a small number of
threads in the thread group - say 10 threads, ramping over 10 seconds. But
fails with the symtoms reported with 40 threads ramping over 10 seconds. And
I don't think I'm getting caught by the thread shutdown time - (I've allowed
it hours while investigating). I also doubt it's directly the number of
threads that's the factor, but more how many are underway when the assertion
kicks in and the "Stop Test" functionality tries to halt the test. It just
seems to "lose control" of the threads being initiated during the "Stop Test"
activity.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org