DO NOT REPLY [Bug 34752] - Jmeter Get Hanged After Cout reaches to 5000 Count.

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

DO NOT REPLY [Bug 34752] - Jmeter Get Hanged After Cout reaches to 5000 Count.

Bugzilla from bugzilla@apache.org
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=34752>.
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=34752





------- Additional Comments From [hidden email]  2005-05-06 12:54 -------
Can't see anything obvious in the log, except the test run seems very short -
Thread Group1-1 starts at 09:36:07 and finishes at 09:36:17. Others take
longer, but the total run-time is only 10 minutes or so.

I suggest you upgrade to 2.0.3, as that has quite a few fixes compared with
2.0.1.

Might be worth increasing the ramp-up to 150.

Also, when you say that JMeter hangs, does it eventually complete?
Or do some threads never finish, even if you wait for several minutes?
If running in GUI mode, does JMeter successfully process the Stop command?

You wrote:
"For the This Thread Group It always Gives the Jmeter Response as Not
Responding"
Can you explain what you mean by this?

--
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: [hidden email]
For additional commands, e-mail: [hidden email]