Test plan stopped working after increasing thread count

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Test plan stopped working after increasing thread count

David Balažic
Hi!

I made a test plan in JMeter 5.3 with some JDBC Request samplers.

It worked fine, until I increased the number of threads parameter in the (only) thread group element from 1 to 2.

In the next run about 30 test steps were executed, then the test stopped.
I started in the GUI, watching results in "Summary Report" listener.

After changing the thread count back to 1, it still did not work.
When I start the test, it just stop after a second.

Here is the log:


2020-07-16 17:55:10,543 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2020-07-16 17:55:10,543 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2020-07-16 17:55:10,547 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, *local*)
2020-07-16 17:55:10,585 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : myThreadGroup.
2020-07-16 17:55:10,585 INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group addRoleToUser  tests.
2020-07-16 17:55:10,585 INFO o.a.j.e.StandardJMeterEngine: Test will stop on error
2020-07-16 17:55:10,585 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=0 delayedStart=false
2020-07-16 17:55:10,586 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2020-07-16 17:55:10,586 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2020-07-16 17:55:10,587 INFO o.a.j.t.JMeterThread: Thread started: addRoleToUser  tests 1-1
2020-07-16 17:55:10,753 INFO o.a.j.t.JMeterThread: Shutdown Test detected by thread: addRoleToUser  tests 1-1
2020-07-16 17:55:10,753 INFO o.a.j.t.JMeterThread: Thread finished: addRoleToUser  tests 1-1
2020-07-16 17:55:10,754 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2020-07-16 17:55:10,757 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, *local*)


I compared the JMX file to an older version and there are no changes.

What could be wrong? Where to look?
Increasing log level does not say anything useful. It shows an SQL is about to be started, then the Shutdown Test detected by thread is printed.
Restarting JMeter also does not help.


Lep pozdrav,
David Balažic


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Test plan stopped working after increasing thread count

Martin Grigorov
Hi David,

On Thu, Jul 16, 2020 at 7:06 PM David Balažic <[hidden email]>
wrote:

> Hi!
>
> I made a test plan in JMeter 5.3 with some JDBC Request samplers.
>
> It worked fine, until I increased the number of threads parameter in the
> (only) thread group element from 1 to 2.
>
> In the next run about 30 test steps were executed, then the test stopped.
> I started in the GUI, watching results in "Summary Report" listener.
>
> After changing the thread count back to 1, it still did not work.
> When I start the test, it just stop after a second.
>
> Here is the log:
>
>
> 2020-07-16 17:55:10,543 INFO o.a.j.e.StandardJMeterEngine: Running the
> test!
> 2020-07-16 17:55:10,543 INFO o.a.j.s.SampleEvent: List of
> sample_variables: []
> 2020-07-16 17:55:10,547 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true,
> *local*)
> 2020-07-16 17:55:10,585 INFO o.a.j.e.StandardJMeterEngine: Starting
> ThreadGroup: 1 : myThreadGroup.
> 2020-07-16 17:55:10,585 INFO o.a.j.e.StandardJMeterEngine: Starting 1
> threads for group addRoleToUser  tests.
> 2020-07-16 17:55:10,585 INFO o.a.j.e.StandardJMeterEngine: Test will stop
> on error
> 2020-07-16 17:55:10,585 INFO o.a.j.t.ThreadGroup: Starting thread group...
> number=1 threads=1 ramp-up=0 delayedStart=false
> 2020-07-16 17:55:10,586 INFO o.a.j.t.ThreadGroup: Started thread group
> number 1
> 2020-07-16 17:55:10,586 INFO o.a.j.e.StandardJMeterEngine: All thread
> groups have been started
> 2020-07-16 17:55:10,587 INFO o.a.j.t.JMeterThread: Thread started:
> addRoleToUser  tests 1-1
> 2020-07-16 17:55:10,753 INFO o.a.j.t.JMeterThread: Shutdown Test detected
> by thread: addRoleToUser  tests 1-1
> 2020-07-16 17:55:10,753 INFO o.a.j.t.JMeterThread: Thread finished:
> addRoleToUser  tests 1-1
> 2020-07-16 17:55:10,754 INFO o.a.j.e.StandardJMeterEngine: Notifying test
> listeners of end of test
> 2020-07-16 17:55:10,757 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false,
> *local*)
>
>
> I compared the JMX file to an older version and there are no changes.
>
> What could be wrong? Where to look?
> Increasing log level does not say anything useful. It shows an SQL is
> about to be started, then the Shutdown Test detected by thread is printed.
> Restarting JMeter also does not help.
>
>
A wild guess: is it possible that you have jdbc connections leak and at
some point the DB cannot create new connections anymore.
Try by restarting both the DB and JMeter.


>
> Lep pozdrav,
> David Balažic
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Test plan stopped working after increasing thread count

David Balažic
I restarted even the OS(both client and server), does not help.
Funny, other test plans on the same db work.

Lp,
David


> On 24 Jul 2020, at 09:48, Martin Grigorov <[hidden email]> wrote:
>
> CAUTION: Origin is external! The content might not be safe!
>
>
> Hi David,
>
>> On Thu, Jul 16, 2020 at 7:06 PM David Balažic <[hidden email]>
>> wrote:
>>
>> Hi!
>>
>> I made a test plan in JMeter 5.3 with some JDBC Request samplers.
>>
>> It worked fine, until I increased the number of threads parameter in the
>> (only) thread group element from 1 to 2.
>>
>> In the next run about 30 test steps were executed, then the test stopped.
>> I started in the GUI, watching results in "Summary Report" listener.
>>
>> After changing the thread count back to 1, it still did not work.
>> When I start the test, it just stop after a second.
>>
>> Here is the log:
>>
>>
>> 2020-07-16 17:55:10,543 INFO o.a.j.e.StandardJMeterEngine: Running the
>> test!
>> 2020-07-16 17:55:10,543 INFO o.a.j.s.SampleEvent: List of
>> sample_variables: []
>> 2020-07-16 17:55:10,547 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true,
>> *local*)
>> 2020-07-16 17:55:10,585 INFO o.a.j.e.StandardJMeterEngine: Starting
>> ThreadGroup: 1 : myThreadGroup.
>> 2020-07-16 17:55:10,585 INFO o.a.j.e.StandardJMeterEngine: Starting 1
>> threads for group addRoleToUser  tests.
>> 2020-07-16 17:55:10,585 INFO o.a.j.e.StandardJMeterEngine: Test will stop
>> on error
>> 2020-07-16 17:55:10,585 INFO o.a.j.t.ThreadGroup: Starting thread group...
>> number=1 threads=1 ramp-up=0 delayedStart=false
>> 2020-07-16 17:55:10,586 INFO o.a.j.t.ThreadGroup: Started thread group
>> number 1
>> 2020-07-16 17:55:10,586 INFO o.a.j.e.StandardJMeterEngine: All thread
>> groups have been started
>> 2020-07-16 17:55:10,587 INFO o.a.j.t.JMeterThread: Thread started:
>> addRoleToUser  tests 1-1
>> 2020-07-16 17:55:10,753 INFO o.a.j.t.JMeterThread: Shutdown Test detected
>> by thread: addRoleToUser  tests 1-1
>> 2020-07-16 17:55:10,753 INFO o.a.j.t.JMeterThread: Thread finished:
>> addRoleToUser  tests 1-1
>> 2020-07-16 17:55:10,754 INFO o.a.j.e.StandardJMeterEngine: Notifying test
>> listeners of end of test
>> 2020-07-16 17:55:10,757 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false,
>> *local*)
>>
>>
>> I compared the JMX file to an older version and there are no changes.
>>
>> What could be wrong? Where to look?
>> Increasing log level does not say anything useful. It shows an SQL is
>> about to be started, then the Shutdown Test detected by thread is printed.
>> Restarting JMeter also does not help.
>>
>>
> A wild guess: is it possible that you have jdbc connections leak and at
> some point the DB cannot create new connections anymore.
> Try by restarting both the DB and JMeter.
>
>
>>
>> Lep pozdrav,
>> David Balažic
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]