so to summarize. It appears to work for 2 minutes, but for 2 hours it doesn't.
maybe there was an exception, which caused the test to stop unexpectedly. the only thing I can think of is to run the test in Gui mode for 10-15 minutes to see what happens. Hopefully you'll see the error that caused it. I've successfully run stress test ranging from 100K-600K requests. In cases where the test stopped, either I had a bug in my test plan, or the webserver stopped accepting connections and crashed. In some cases, I've seem the webserver stop accepting connections under load, but after the test it is only partially functioning. peter On Fri, 25 Jun 2004 08:37:14 -0700, Mike Darretta <[EMAIL PROTECTED]> wrote: > > I am trying to set up nightly tests using the following scheduler > configuration: > > Loop count: Forever > Scheduler: Enabled > Start time: <date> 07:00:00 <= GMT > Stop time: <date> 09:00:00 > Duration: 7200 > Startup delay: 0 > > I startup the test in Linux in non-GUI mode with the following command: > > $JMETER_BIN/jmeter -n -t plans/test_plan.jmx -l results_file_<timestamp>.jtl > > When I execute this command, I end up with two results files - one for > the start and one for the end of the test. Both files span a only a > single second's worth of data. > > I have tested this configuration for a 2 minute interval, and in this > case I get a single file spanning two minutes. Does anyone have any > thoughts on what I may have done incorrectly? > > Thanx! > > --Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
