You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by sebb <se...@gmail.com> on 2011/10/01 11:26:34 UTC
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
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-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by sebb <se...@gmail.com>.
On 4 October 2011 23:24, Basim Baassiri <ba...@baassiri.ca> wrote:
> Test has ended is not written to the logs
In that case, the bug fix has worked here.
> On Tue, Oct 4, 2011 at 6:04 PM, sebb <se...@gmail.com> wrote:
>
>> On 4 October 2011 22:43, Basim Baassiri <ba...@baassiri.ca> wrote:
>> > I'm experiencing the same issue with the latest release 2.5.1
>>
>> Does it say "Test has ended" ?
>>
>> > On Sun, Oct 2, 2011 at 9:57 AM, sebb <se...@gmail.com> wrote:
>> >
>> >> 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 <se...@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-unsubscribe@jakarta.apache.org
>> >> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >> >>
>> >> >>
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by sebb <se...@gmail.com>.
On 5 October 2011 18:14, Basim Baassiri <ba...@baassiri.ca> wrote:
> my comments inline. I have a workaround and wanted to share my findings
>
> On Tue, Oct 4, 2011 at 8:09 PM, sebb <se...@gmail.com> wrote:
>
>> On 4 October 2011 23:31, Basim Baassiri <ba...@baassiri.ca> wrote:
>> > my current observations are the initial 90 threads start and finish and
>> the
>> > remainder appear to be not shutting down
>> >
>> > There is a period of almost 55 mins where the logs are not being written
>> to
>> > at which point i see another thread shutdown message
>>
>> So?
>>
>> That just means that some threads are not completing, or are taking a
>> long time to do so.
>>
>> You need to find out why.
>>
>
>
> I have retrieve all embedded resources from html files set to true for the
> config element http request. Setting it to false made my test plan finish.
> I.e. i did not encounter threads not completing
>
OK, so one or more embedded resources are not being retrieved in
reasonable time.
>
>>
>> A thread dump should indicate why the threads have not finished.
>> Most likely they are waiting for a sample to complete.
>>
>> However, there are other possibilities, e.g. deadlock.
>>
>> Thread dumps tend to be very large, so save it to a file on a public
>> server and send the URL rather than posting here.
>>
>
>
> I generated a thread dump (ctrl-break) in windows
> Here it is
> http://pastie.org/pastes/2644312/text
>
Looks like several samplers are waiting for a response from the remote system.
>
>>
>> [Also, it's much harder reading long logs etc in mail messages,
>> because wrapping destroys the formatting.]
>>
>>
> agreed.
>
>
>> If the sampler supports it, you might wish to consider adding a
>> timeout; make this somewhat longer than the longest expected response
>> so you don't lose any valid responses. A few minutes might be
>> suitable, or it might have to be longer.
>>
>>
> I placed a timeout on the http response and my problem of the tests not
> finishing went away but the number of fails increased
And what were the failed samples?
Is there a pattern to them?
Can you download them with a browser?
There is no sign that JMeter is at fault here, merely that some of the
HTTP resources it has detected and tries to download are not
responding, or are responding extremely slowly.
If necessary, exclude those resources from the ones JMeter downloads.
>
>> <snip log file entries>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by Basim Baassiri <ba...@baassiri.ca>.
my comments inline. I have a workaround and wanted to share my findings
On Tue, Oct 4, 2011 at 8:09 PM, sebb <se...@gmail.com> wrote:
> On 4 October 2011 23:31, Basim Baassiri <ba...@baassiri.ca> wrote:
> > my current observations are the initial 90 threads start and finish and
> the
> > remainder appear to be not shutting down
> >
> > There is a period of almost 55 mins where the logs are not being written
> to
> > at which point i see another thread shutdown message
>
> So?
>
> That just means that some threads are not completing, or are taking a
> long time to do so.
>
> You need to find out why.
>
I have retrieve all embedded resources from html files set to true for the
config element http request. Setting it to false made my test plan finish.
I.e. i did not encounter threads not completing
>
> A thread dump should indicate why the threads have not finished.
> Most likely they are waiting for a sample to complete.
>
> However, there are other possibilities, e.g. deadlock.
>
> Thread dumps tend to be very large, so save it to a file on a public
> server and send the URL rather than posting here.
>
I generated a thread dump (ctrl-break) in windows
Here it is
http://pastie.org/pastes/2644312/text
>
> [Also, it's much harder reading long logs etc in mail messages,
> because wrapping destroys the formatting.]
>
>
agreed.
> If the sampler supports it, you might wish to consider adding a
> timeout; make this somewhat longer than the longest expected response
> so you don't lose any valid responses. A few minutes might be
> suitable, or it might have to be longer.
>
>
I placed a timeout on the http response and my problem of the tests not
finishing went away but the number of fails increased
> <snip log file entries>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by sebb <se...@gmail.com>.
On 4 October 2011 23:31, Basim Baassiri <ba...@baassiri.ca> wrote:
> my current observations are the initial 90 threads start and finish and the
> remainder appear to be not shutting down
>
> There is a period of almost 55 mins where the logs are not being written to
> at which point i see another thread shutdown message
So?
That just means that some threads are not completing, or are taking a
long time to do so.
You need to find out why.
A thread dump should indicate why the threads have not finished.
Most likely they are waiting for a sample to complete.
However, there are other possibilities, e.g. deadlock.
Thread dumps tend to be very large, so save it to a file on a public
server and send the URL rather than posting here.
[Also, it's much harder reading long logs etc in mail messages,
because wrapping destroys the formatting.]
If the sampler supports it, you might wish to consider adding a
timeout; make this somewhat longer than the longest expected response
so you don't lose any valid responses. A few minutes might be
suitable, or it might have to be longer.
<snip log file entries>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by Basim Baassiri <ba...@baassiri.ca>.
my current observations are the initial 90 threads start and finish and the
remainder appear to be not shutting down
There is a period of almost 55 mins where the logs are not being written to
at which point i see another thread shutdown message
2011/10/04 17:07:40 INFO - jmeter.util.JMeterUtils: Setting Locale to
en_US
2011/10/04 17:07:40 INFO - jmeter.JMeter: Loading user properties from:
C:\jakarta-jmeter-2.5.1\bin\user.properties
2011/10/04 17:07:40 INFO - jmeter.JMeter: Loading system properties from:
C:\jakarta-jmeter-2.5.1\bin\system.properties
2011/10/04 17:07:40 INFO - jmeter.JMeter: Copyright (c) 1998-2011 The
Apache Software Foundation
2011/10/04 17:07:40 INFO - jmeter.JMeter: Version 2.5.1 r1177103
2011/10/04 17:07:40 INFO - jmeter.JMeter: java.version=1.6.0_21
2011/10/04 17:07:40 INFO - jmeter.JMeter: java.vm.name=Java HotSpot(TM)
64-Bit Server VM
2011/10/04 17:07:40 INFO - jmeter.JMeter: os.name=Windows 7
2011/10/04 17:07:40 INFO - jmeter.JMeter: os.arch=amd64
2011/10/04 17:07:40 INFO - jmeter.JMeter: os.version=6.1
2011/10/04 17:07:40 INFO - jmeter.JMeter: file.encoding=Cp1252
2011/10/04 17:07:40 INFO - jmeter.JMeter: Default Locale=English (United
States)
2011/10/04 17:07:40 INFO - jmeter.JMeter: JMeter Locale=English (United
States)
2011/10/04 17:07:40 INFO - jmeter.JMeter:
JMeterHome=C:\jakarta-jmeter-2.5.1
2011/10/04 17:07:40 INFO - jmeter.JMeter: user.dir
=C:\jakarta-jmeter-2.5.1\bin
2011/10/04 17:07:40 INFO - jmeter.JMeter: PWD
=C:\jakarta-jmeter-2.5.1\bin
2011/10/04 17:07:40 INFO - jmeter.JMeter: Loaded icon properties from
org/apache/jmeter/images/icon.properties
2011/10/04 17:07:41 INFO - jmeter.engine.util.CompoundVariable: Note:
Function class names must contain the string: '.functions.'
2011/10/04 17:07:41 INFO - jmeter.engine.util.CompoundVariable: Note:
Function class names must not contain the string: '.gui.'
2011/10/04 17:07:42 INFO - jmeter.util.BSFTestElement: Registering JMeter
version of JavaScript engine as work-round for BSF-22
2011/10/04 17:07:42 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase:
Cannot find .className property for htmlParser, using default
2011/10/04 17:07:42 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase:
Parser for text/html is
2011/10/04 17:07:42 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase:
Parser for application/xhtml+xml is
2011/10/04 17:07:42 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase:
Parser for application/xml is
2011/10/04 17:07:42 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase:
Parser for text/xml is
2011/10/04 17:07:42 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase:
Parser for text/vnd.wap.wml is
org.apache.jmeter.protocol.http.parser.RegexpHTMLParser
2011/10/04 17:07:42 INFO - jmeter.protocol.http.sampler.HTTPSamplerBase:
Reuse SSL session context on subsequent iterations: true
2011/10/04 17:07:43 INFO - jmeter.protocol.http.control.CookieManager:
Settings: Delete null: true Check: true Allow variable: true Save: false
Prefix: COOKIE_
2011/10/04 17:07:43 INFO - jmeter.gui.util.MenuFactory: Skipping
org.apache.jmeter.protocol.http.modifier.gui.ParamModifierGui
2011/10/04 17:07:43 INFO - jmeter.gui.util.MenuFactory: Skipping
org.apache.jmeter.protocol.http.modifier.gui.UserParameterModifierGui
2011/10/04 17:07:44 INFO - jmeter.samplers.SampleResult: Note: Sample
TimeStamps are START times
2011/10/04 17:07:44 INFO - jmeter.samplers.SampleResult:
sampleresult.default.encoding is set to ISO-8859-1
2011/10/04 17:07:44 INFO - jmeter.samplers.SampleResult:
sampleresult.useNanoTime=true
2011/10/04 17:07:48 INFO - jmeter.services.FileServer: Default
base='C:\jakarta-jmeter-2.5.1\bin'
2011/10/04 17:07:48 INFO - jmeter.gui.action.Load: Loading file:
C:\Temp\prodperftest\test\jmeter\TestNavigation100.jmx
2011/10/04 17:07:48 INFO - jmeter.services.FileServer: Set new base
'C:\Temp\prodperftest\test\jmeter'
2011/10/04 17:07:48 INFO - jmeter.save.SaveService: Testplan (JMX) version:
2.2. Testlog (JTL) version: 2.2
2011/10/04 17:07:48 INFO - jmeter.save.SaveService: Using SaveService
properties file encoding UTF-8
2011/10/04 17:07:48 INFO - jmeter.save.SaveService: Using SaveService
properties file version 1050447
2011/10/04 17:07:48 INFO - jmeter.save.SaveService: Using SaveService
properties version 2.1
2011/10/04 17:07:48 INFO - jmeter.save.SaveService: All converter versions
present and correct
2011/10/04 17:07:48 INFO - jmeter.services.FileServer: Set new
base='C:\Temp\prodperftest\test\jmeter'
2011/10/04 17:07:52 INFO - jmeter.engine.StandardJMeterEngine: Listeners
will be started after enabling running version
2011/10/04 17:07:52 INFO - jmeter.engine.StandardJMeterEngine: To revert to
the earlier behaviour, define jmeterengine.startlistenerslater=false
2011/10/04 17:07:52 INFO - jmeter.engine.StandardJMeterEngine: Running the
test!
2011/10/04 17:07:52 INFO - jmeter.gui.util.JMeterMenuBar:
setRunning(true,*local*)
2011/10/04 17:07:52 INFO - jmeter.engine.StandardJMeterEngine: Starting 100
threads for group Thread Group.
2011/10/04 17:07:52 INFO - jmeter.engine.StandardJMeterEngine: Thread will
continue on error
2011/10/04 17:07:52 INFO - jmeter.threads.JMeterThread:
jmeterthread.startearlier=true (see jmeter.properties)
2011/10/04 17:07:52 INFO - jmeter.threads.JMeterThread: Running
PostProcessors in forward order
2011/10/04 17:07:52 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-1
2011/10/04 17:07:52 INFO - jmeter.protocol.http.sampler.HTTPJavaImpl:
Maximum connection retries = 10
2011/10/04 17:07:52 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-2
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-3
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-4
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-5
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-6
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-7
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-8
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-9
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-10
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-11
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-12
2011/10/04 17:07:53 INFO - jmeter.engine.StandardJMeterEngine: All threads
have been started
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-13
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-14
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-15
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-16
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-17
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-18
2011/10/04 17:07:53 INFO - jmeter.util.JsseSSLManager: Using default SSL
protocol: TLS
2011/10/04 17:07:53 INFO - jmeter.util.JsseSSLManager: SSL session context:
per-thread
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: JmeterKeyStore Location:
C:\Users\bbaassiri\.keystore
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: JmeterKeyStore Location:
C:\Users\bbaassiri\.keystore
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: JmeterKeyStore Location:
C:\Users\bbaassiri\.keystore
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: JmeterKeyStore Location:
C:\Users\bbaassiri\.keystore
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: JmeterKeyStore Location:
C:\Users\bbaassiri\.keystore
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: KeyStore created OK,
Type: JKS
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: KeyStore created OK,
Type: JKS
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: KeyStore created OK,
Type: JKS
2011/10/04 17:07:53 WARN - jmeter.util.SSLManager: Keystore file not found,
loading empty keystore
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: KeyStore created OK,
Type: JKS
2011/10/04 17:07:53 WARN - jmeter.util.SSLManager: Keystore file not found,
loading empty keystore
2011/10/04 17:07:53 WARN - jmeter.util.SSLManager: Keystore file not found,
loading empty keystore
2011/10/04 17:07:53 WARN - jmeter.util.SSLManager: Keystore file not found,
loading empty keystore
2011/10/04 17:07:53 INFO - jmeter.util.SSLManager: KeyStore created OK,
Type: JKS
2011/10/04 17:07:53 WARN - jmeter.util.SSLManager: Keystore file not found,
loading empty keystore
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-19
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-20
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-21
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-22
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-24
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-25
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-23
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-27
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-29
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-26
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-28
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-30
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-32
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-31
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-33
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-34
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-35
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-36
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-37
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-38
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-39
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-40
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-41
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-42
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-44
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-43
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-45
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-46
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-47
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-48
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-49
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-50
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-51
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-52
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-53
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-54
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-55
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-56
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-57
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-58
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-59
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-60
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-61
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-62
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-64
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-65
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-66
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-63
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-67
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-69
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-70
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-68
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-72
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-71
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-73
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-74
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-75
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-79
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-80
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-78
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-81
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-77
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-76
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-82
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-83
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-84
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-85
2011/10/04 17:07:53 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-86
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-87
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-88
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-89
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-90
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-91
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-92
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-93
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-94
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-95
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-96
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-97
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-98
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-99
2011/10/04 17:07:54 INFO - jmeter.threads.JMeterThread: Thread started:
Thread Group 1-100
2011/10/04 17:08:04 INFO -
jmeter.protocol.http.parser.HtmlParserHTMLParser: Using htmlparser version:
2.0 (Release Build Sep 17, 2006)
2011/10/04 17:08:04 INFO -
jmeter.protocol.http.parser.HtmlParserHTMLParser: Using htmlparser version:
2.0 (Release Build Sep 17, 2006)
2011/10/04 17:08:04 INFO - jmeter.protocol.http.parser.HTMLParser: Created
org.apache.jmeter.protocol.http.parser.HtmlParserHTMLParser
2011/10/04 17:08:04 INFO - jmeter.protocol.http.parser.HTMLParser: Created
org.apache.jmeter.protocol.http.parser.HtmlParserHTMLParser
2011/10/04 17:16:42 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-37
2011/10/04 17:16:42 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-37
2011/10/04 17:17:38 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-12
2011/10/04 17:17:38 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-12
2011/10/04 17:17:43 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-1
2011/10/04 17:17:43 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-1
2011/10/04 17:17:57 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-77
2011/10/04 17:17:57 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-77
2011/10/04 17:17:57 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-48
2011/10/04 17:17:57 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-48
2011/10/04 17:17:58 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-17
2011/10/04 17:17:58 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-17
2011/10/04 17:18:07 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-54
2011/10/04 17:18:07 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-54
2011/10/04 17:18:10 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-62
2011/10/04 17:18:10 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-62
2011/10/04 17:18:19 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-36
2011/10/04 17:18:19 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-36
2011/10/04 17:18:20 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-8
2011/10/04 17:18:20 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-8
2011/10/04 17:18:25 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-87
2011/10/04 17:18:25 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-87
2011/10/04 17:18:32 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-43
2011/10/04 17:18:32 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-43
2011/10/04 17:18:37 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-96
2011/10/04 17:18:37 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-96
2011/10/04 17:18:38 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-6
2011/10/04 17:18:38 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-6
2011/10/04 17:18:42 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-3
2011/10/04 17:18:42 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-3
2011/10/04 17:18:43 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-68
2011/10/04 17:18:43 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-68
2011/10/04 17:18:44 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-34
2011/10/04 17:18:44 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-34
2011/10/04 17:18:47 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-73
2011/10/04 17:18:47 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-73
2011/10/04 17:18:48 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-83
2011/10/04 17:18:48 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-83
2011/10/04 17:18:48 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-44
2011/10/04 17:18:48 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-44
2011/10/04 17:18:48 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-97
2011/10/04 17:18:48 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-97
2011/10/04 17:18:49 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-67
2011/10/04 17:18:49 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-67
2011/10/04 17:18:50 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-40
2011/10/04 17:18:50 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-40
2011/10/04 17:18:50 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-84
2011/10/04 17:18:50 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-84
2011/10/04 17:18:51 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-86
2011/10/04 17:18:51 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-86
2011/10/04 17:18:52 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-26
2011/10/04 17:18:52 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-26
2011/10/04 17:18:56 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-94
2011/10/04 17:18:56 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-94
2011/10/04 17:18:59 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-31
2011/10/04 17:18:59 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-31
2011/10/04 17:19:00 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-4
2011/10/04 17:19:00 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-4
2011/10/04 17:19:00 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-69
2011/10/04 17:19:00 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-69
2011/10/04 17:19:02 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-100
2011/10/04 17:19:02 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-100
2011/10/04 17:19:03 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-15
2011/10/04 17:19:03 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-15
2011/10/04 17:19:04 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-74
2011/10/04 17:19:04 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-74
2011/10/04 17:19:05 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-58
2011/10/04 17:19:05 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-58
2011/10/04 17:19:15 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-85
2011/10/04 17:19:15 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-85
2011/10/04 17:19:15 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-66
2011/10/04 17:19:15 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-66
2011/10/04 17:19:16 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-29
2011/10/04 17:19:16 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-29
2011/10/04 17:19:16 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-47
2011/10/04 17:19:16 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-47
2011/10/04 17:19:17 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-90
2011/10/04 17:19:17 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-90
2011/10/04 17:19:17 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-32
2011/10/04 17:19:17 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-32
2011/10/04 17:19:18 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-9
2011/10/04 17:19:18 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-9
2011/10/04 17:19:18 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-49
2011/10/04 17:19:18 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-49
2011/10/04 17:19:19 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-11
2011/10/04 17:19:19 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-11
2011/10/04 17:19:19 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-80
2011/10/04 17:19:19 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-80
2011/10/04 17:19:19 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-65
2011/10/04 17:19:19 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-65
2011/10/04 17:19:20 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-27
2011/10/04 17:19:20 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-27
2011/10/04 17:19:21 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-71
2011/10/04 17:19:21 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-71
2011/10/04 17:19:22 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-30
2011/10/04 17:19:22 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-30
2011/10/04 17:19:25 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-45
2011/10/04 17:19:25 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-45
2011/10/04 17:19:28 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-52
2011/10/04 17:19:28 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-52
2011/10/04 17:19:31 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-5
2011/10/04 17:19:31 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-5
2011/10/04 17:19:32 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-99
2011/10/04 17:19:32 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-99
2011/10/04 17:19:33 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-39
2011/10/04 17:19:33 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-39
2011/10/04 17:19:34 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-51
2011/10/04 17:19:34 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-51
2011/10/04 17:19:34 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-46
2011/10/04 17:19:34 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-46
2011/10/04 17:19:35 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-41
2011/10/04 17:19:35 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-41
2011/10/04 17:19:36 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-61
2011/10/04 17:19:36 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-61
2011/10/04 17:19:38 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-42
2011/10/04 17:19:38 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-42
2011/10/04 17:19:40 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-98
2011/10/04 17:19:40 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-98
2011/10/04 17:19:41 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-88
2011/10/04 17:19:41 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-88
2011/10/04 17:19:42 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-28
2011/10/04 17:19:42 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-28
2011/10/04 17:19:43 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-7
2011/10/04 17:19:43 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-7
2011/10/04 17:19:45 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-72
2011/10/04 17:19:45 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-72
2011/10/04 17:19:46 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-23
2011/10/04 17:19:46 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-23
2011/10/04 17:19:46 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-14
2011/10/04 17:19:46 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-14
2011/10/04 17:19:48 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-55
2011/10/04 17:19:48 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-55
2011/10/04 17:19:49 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-81
2011/10/04 17:19:49 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-81
2011/10/04 17:19:49 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-20
2011/10/04 17:19:49 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-20
2011/10/04 17:19:50 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-21
2011/10/04 17:19:50 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-21
2011/10/04 17:19:51 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-2
2011/10/04 17:19:51 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-2
2011/10/04 17:19:52 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-79
2011/10/04 17:19:52 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-79
2011/10/04 17:19:53 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-53
2011/10/04 17:19:53 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-53
2011/10/04 17:19:54 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-92
2011/10/04 17:19:54 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-92
2011/10/04 17:19:54 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-25
2011/10/04 17:19:54 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-25
2011/10/04 17:19:54 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-78
2011/10/04 17:19:54 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-78
2011/10/04 17:19:57 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-35
2011/10/04 17:19:57 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-35
2011/10/04 17:19:57 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-24
2011/10/04 17:19:57 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-24
2011/10/04 17:19:58 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-76
2011/10/04 17:19:58 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-76
2011/10/04 17:19:59 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-56
2011/10/04 17:19:59 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-56
2011/10/04 17:19:59 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-91
2011/10/04 17:19:59 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-91
2011/10/04 17:20:00 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-63
2011/10/04 17:20:00 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-63
2011/10/04 17:20:01 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-50
2011/10/04 17:20:01 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-50
2011/10/04 17:20:01 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-64
2011/10/04 17:20:01 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-64
2011/10/04 17:20:08 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-13
2011/10/04 17:20:08 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-13
2011/10/04 17:20:10 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-89
2011/10/04 17:20:10 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-89
2011/10/04 17:20:15 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-82
2011/10/04 17:20:15 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-82
2011/10/04 17:21:04 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-18
2011/10/04 17:21:04 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-18
2011/10/04 17:21:20 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-33
2011/10/04 17:21:20 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-33
2011/10/04 18:14:05 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-70
2011/10/04 18:14:05 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-70
2011/10/04 18:17:04 INFO - jmeter.threads.JMeterThread: Thread finished:
Thread Group 1-93
2011/10/04 18:17:04 INFO - jmeter.engine.StandardJMeterEngine: Ending
thread Thread Group 1-93
On Tue, Oct 4, 2011 at 6:24 PM, Basim Baassiri <ba...@baassiri.ca> wrote:
> Test has ended is not written to the logs
>
>
> On Tue, Oct 4, 2011 at 6:04 PM, sebb <se...@gmail.com> wrote:
>
>> On 4 October 2011 22:43, Basim Baassiri <ba...@baassiri.ca> wrote:
>> > I'm experiencing the same issue with the latest release 2.5.1
>>
>> Does it say "Test has ended" ?
>>
>> > On Sun, Oct 2, 2011 at 9:57 AM, sebb <se...@gmail.com> wrote:
>> >
>> >> 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 <se...@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-unsubscribe@jakarta.apache.org
>> >> >> For additional commands, e-mail:
>> jmeter-user-help@jakarta.apache.org
>> >> >>
>> >> >>
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by Basim Baassiri <ba...@baassiri.ca>.
Test has ended is not written to the logs
On Tue, Oct 4, 2011 at 6:04 PM, sebb <se...@gmail.com> wrote:
> On 4 October 2011 22:43, Basim Baassiri <ba...@baassiri.ca> wrote:
> > I'm experiencing the same issue with the latest release 2.5.1
>
> Does it say "Test has ended" ?
>
> > On Sun, Oct 2, 2011 at 9:57 AM, sebb <se...@gmail.com> wrote:
> >
> >> 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 <se...@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-unsubscribe@jakarta.apache.org
> >> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >>
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by sebb <se...@gmail.com>.
On 4 October 2011 22:43, Basim Baassiri <ba...@baassiri.ca> wrote:
> I'm experiencing the same issue with the latest release 2.5.1
Does it say "Test has ended" ?
> On Sun, Oct 2, 2011 at 9:57 AM, sebb <se...@gmail.com> wrote:
>
>> 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 <se...@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-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by Basim Baassiri <ba...@baassiri.ca>.
I'm experiencing the same issue with the latest release 2.5.1
On Sun, Oct 2, 2011 at 9:57 AM, sebb <se...@gmail.com> wrote:
> 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 <se...@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-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by sebb <se...@gmail.com>.
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 <se...@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-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: not all thread group ending with nothing in the logs WARN Thread
won't exit after stopping
Posted by Basim Baassiri <ba...@baassiri.ca>.
HI
just to confirm that this is the bug that might resolve my issue
https://issues.apache.org/bugzilla/show_bug.cgi?id=51880
On Sat, Oct 1, 2011 at 5:26 AM, sebb <se...@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-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>