Were you running in client-server mode? I don't see how JMeter can continue running after you exit JMeter - it does not spawn any additional copies of the JVM.
However, if you stop the client, it is possible that the server will continue. [That should be fixed in the next release.] S. On 02/09/07, jada <[EMAIL PROTECTED]> wrote: > > Hello all, > > I ran a test with 3000 threads and ramp-up 1000 seconds against a Tomcat > server with a back-end Oracle database. > > After a while when the Samples# reached around 1000, the Error% was > increasing then I stopped the test and exited JMeter completely. I opened > the Task Manager and found a java.exe still in the Processes list. I just > left it alone because I thought JMeter had been killed and that java.exe was > something else. > > Since then the web app could not access the Oracle database anymore. The > Tomcat server had to be restarted to release whatever seemed to be stuck. > > I tried running the test the second time. The Error% appeared sooner when > the Samples# reached around 150. I stopped the test and exited JMeter > completely. Then I opened the jmeter.log file to take a look. Surprisingly, > I found threads left over from the first test (based on Thread labels) > mixing within the second one. > > A snap-shot of the log follows for illustration. As you can see, at time > 20:35:34 the last Thread to be created in the second test was "Thread Group > 1-194" before the test was stopping. It's interesting that "Thread Group > 1-1515", "Thread Group 1-1738", etc. were stopped and started at the very > end. Apparently these threads were left from the first test and still alive > after the first test had been terminated and JMeter had exited. > > Again, I opened the Task Manager and found a java.exe still in the Processes > list. I killed it several times before it disappeared. > > My guess is that after the first JMeter test was stopped, the process was > still running in the background and continued writing to the same log. > Therefore the log has mixed information of the 2 tests. > > ______________________________ > > 2007/09/01 20:34:55 INFO - jmeter.engine.StandardJMeterEngine: Starting > 3000 threads for group Thread Group. Ramp up = 1000. > 2007/09/01 20:34:55 INFO - jmeter.engine.StandardJMeterEngine: Continue on > error > 2007/09/01 20:34:55 WARN - jmeter.threads.JMeterThread: > jmeterthread.startearlier=true (see jmeter.properties) > 2007/09/01 20:34:55 INFO - jmeter.threads.JMeterThread: Running > PostProcessors in forward order > 2007/09/01 20:34:55 INFO - jmeter.threads.JMeterThread: Thread Thread Group > 1-1 started > 2007/09/01 20:34:55 INFO - jmeter.threads.JMeterThread: Thread Thread Group > 1-2 started > 2007/09/01 20:34:55 INFO - jmeter.threads.JMeterThread: Thread Thread Group > 1-3 started > . . . . . > . . . . . > 2007/09/01 20:35:34 INFO - jmeter.threads.JMeterThread: Thread Thread Group > 1-194 started > 2007/09/01 20:35:34 ERROR - jmeter.protocol.http.sampler.HTTPSampler: > readResponse: java.io.IOException: Server returned HTTP response code: 500 > for URL: http://10.1.10.100/foobar > 2007/09/01 20:35:34 ERROR - jmeter.protocol.http.sampler.HTTPSampler: Cause: > java.io.IOException: Server returned HTTP response code: 500 for URL: > http://10.1.10.100/foobar > 2007/09/01 20:35:34 INFO - jmeter.protocol.http.sampler.HTTPSampler: Error > Response Code: 500 > 2007/09/01 20:35:34 INFO - jmeter.threads.JMeterThread: Stopping Thread > Group 1-1515 > 2007/09/01 20:35:34 INFO - jmeter.threads.JMeterThread: Stopping Thread > Group 1-1738 > 2007/09/01 20:35:34 INFO - jmeter.threads.JMeterThread: Thread Thread Group > 1-1515 started > 2007/09/01 20:35:34 INFO - jmeter.threads.JMeterThread: Stopping Thread > Group 1-2769 > 2007/09/01 20:35:34 INFO - jmeter.threads.JMeterThread: Thread Thread Group > 1-1738 started > 2007/09/01 20:35:34 INFO - jmeter.threads.JMeterThread: Stopping Thread > Group 1-1748 > 2007/09/01 20:35:34 INFO - jmeter.threads.JMeterThread: Thread Thread Group > 1-1515 is done > . . . . . > . . . . . > ______________________________ > > -- > View this message in context: > http://www.nabble.com/Threads-still-running-after-JMeter-exits-tf4367008.html#a12447117 > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
