On 1 October 2011 15:52, Basim Baassiri <ba...@baassiri.ca> wrote: > HI > just to confirm that this is the bug that might resolve my issue > https://issues.apache.org/bugzilla/show_bug.cgi?id=51880
Not exactly - that was a bug exposed/caused by a previous fix to shutdown handling. Please wait until 2.5.1 is released and try again with that. > > On Sat, Oct 1, 2011 at 5:26 AM, sebb <seb...@gmail.com> wrote: > >> On 30 September 2011 20:49, Basim Baassiri <ba...@baassiri.ca> wrote: >> > Hi, >> > I started jmeter with DEBUG logging on (running on window 7) >> > jmeter -Ljmeter.engine=DEBUG >> > >> > i have a test plan that I've seen work and run against a test environment >> > and when i start the testplan against a different environment, jmeter >> > appears to not respond or be active. There is a period of time in the >> logs >> > that nothing happens so i stopped the test >> > >> > 2011/09/30 15:33:39 INFO - jmeter.gui.action.Start: Stopping test >> > 2011/09/30 15:33:39 INFO - jmeter.threads.JMeterThread: Stopping: Thread >> > Group 1-30 >> > 2011/09/30 15:33:39 WARN - jmeter.threads.JMeterThread: Interrupting: >> > Thread Group 1-30 sampler: Product Tab >> > 2011/09/30 15:33:39 INFO - jmeter.threads.JMeterThread: Stopping: Thread >> > Group 1-24 >> > 2011/09/30 15:33:39 WARN - jmeter.threads.JMeterThread: Interrupting: >> > Thread Group 1-24 sampler: Program Tab >> > 2011/09/30 15:33:39 INFO - jmeter.threads.JMeterThread: Stopping: Thread >> > Group 1-9 >> > 2011/09/30 15:33:39 WARN - jmeter.threads.JMeterThread: Interrupting: >> > Thread Group 1-9 sampler: Contract Tab >> > 2011/09/30 15:33:41 INFO - jmeter.threads.JMeterThread: Thread finished: >> > Thread Group 1-9 >> > 2011/09/30 15:33:41 INFO - jmeter.engine.StandardJMeterEngine: Ending >> > thread Thread Group 1-9 >> > 2011/09/30 15:33:42 INFO - jmeter.threads.JMeterThread: Thread finished: >> > Thread Group 1-30 >> > 2011/09/30 15:33:42 INFO - jmeter.engine.StandardJMeterEngine: Ending >> > thread Thread Group 1-30 >> > 2011/09/30 15:33:46 WARN - jmeter.engine.StandardJMeterEngine: Thread >> won't >> > exit: Thread Group 1-24 >> > 2011/09/30 15:33:49 INFO - jmeter.threads.JMeterThread: Thread finished: >> > Thread Group 1-24 >> > 2011/09/30 15:33:49 INFO - jmeter.engine.StandardJMeterEngine: Ending >> > thread Thread Group 1-24 >> > 2011/09/30 15:33:49 INFO - jmeter.engine.StandardJMeterEngine: Stopping >> > test >> > 2011/09/30 15:33:49 INFO - jmeter.engine.StandardJMeterEngine: Notifying >> > test listeners of end of test >> > 2011/09/30 15:33:49 INFO - jmeter.gui.util.JMeterMenuBar: >> > setRunning(false,*local*) >> > 2011/09/30 15:33:49 INFO - jmeter.engine.StandardJMeterEngine: Test has >> > ended >> > 2011/09/30 15:33:51 INFO - jmeter.engine.StandardJMeterEngine: Notifying >> > test listeners of end of test >> > 2011/09/30 15:33:51 INFO - jmeter.gui.util.JMeterMenuBar: >> > setRunning(false,*local*) >> > 2011/09/30 15:33:51 INFO - jmeter.engine.StandardJMeterEngine: Test has >> > ended >> > >> > >> > >> > Any ideas of why the test plan appears to stop >> > >> >> This was due to a bug in the shutdown code, which reported the end of >> the test, even though one or more threads were still running. >> >> This has been fixed in the upcoming 2.5.1, which also allows the user >> to retry the stop command after dismissing the modal dialog. >> >> Note: if some threads refuse to stop, the only solution is to exit the >> JVM; there is no guaranteed safe way to forcibly kill a thread. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
