I just recently checked in a change to the rel 2.0 branch which allows one to use the BeanShell server to shut a test or a thread - see my recent posting in reply to "how can i see which thread is currently being run?(solution to RAMP DOWN!)"
The new methods correspond to the GUI Stop and Shutdown options: stopEngine() = GUI shutdown stopEngineNow() = GUI stop In your case, you'ld probably need to use the stopEngineNow() method, as the others just set a flag and wait for current activity to cease. But at least you could get JMeter to finish up. Perhaps I should add a stopThreadNow() method? == As to the timeout, it might be worth checking the Apache HTTPClient documentation - this is used by the new HTTP Sampler. If there is a timeout facility, it should be quite easy to add it - or it might even already be controllable by a property. Sebastian -----Original Message----- From: Sonam Chauhan [mailto:[EMAIL PROTECTED] Sent: 02 July 2004 08:47 To: 'JMeter Users List' Subject: HTTP timeout setting? Hello JMeter experts! I have been using JMeter to tease out a server bug that only shows up under load. The problem is that when I reproduce this bug, the remote server hangs, but due to the HTTP connections already being made, JMeter hangs too. I run JMeter in non-GUI mode (-n), so I have no easy way to stop the test threads. Is there a HTTP timeout setting that will cause JMeter (or Java) to terminate an HTTP connections if no bytes were transmitted for a timeout duration? With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> PS: Sorry if there is an obvious answer, but a google query on "jmeter http timeout site:jakarta.apache.org" didn't showup anything. ___________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ___________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
