Am 21. August 2019 22:22:58 MESZ schrieb "[email protected]"
<[email protected]>:
> Hi,
>The logging is set for DEBUG already and I don't see any terminated"
>messages at all in jmeter.log.
>I tried a test with only 10 threads for 10 seconds, and endup with
>OS Process Sampler: # Samples = 20
>HTTP Request: # Samples = 10
>So even with much smaller number of threads, the # Samples is still not
>the same.
It could still be the case, that the server could not cope and the http samples
were not processed in time and therefore didn't count.
Can you have a look at the server logs? Did it get all requests? Did it log
them? How long did they take? (note that some servers will log requests quit
the incoming time, so be sure to add the duration of the server requests to
them)
Are the and exceptions or other strange messages in the logs of jmeter? Compare
it to a run with disabled http sampler.
Take threaddumps while running the second second test and see, where jmeter is
spending its time.
>Also the number on the upper left of the Jmeter window is 0/10.
When is it showing those values?
Regards
Felix
>This is really strange :(!!
>Jim
>
>
>On Wednesday, August 21, 2019, 7:32:46 PM UTC, Ivan Rancati
><[email protected]> wrote:
>
>You could try to log with DEBUG level, and see if jmeter.log has
>messages
>like
>"thread 1-37 terminated because the scheduler's time is reached".
>
>Perhaps it's just the web server that takes a long time to answer when
>100
>requests arrive concurrently.
>Running the test for, say, 20 minutes instead of 30 seconds might shed
>some
>light.
>Would the difference between completed OS Process Samplers and
>completed
>HTTP Samplers still be about 80 (therefore much smaller in %), or would
>you
>still have about 1 completed HTTP Sampler for approx. every 4 completed
>OS
>Process Samplers?
>
>Best regards,
>Ivan
>
>On Wed, Aug 21, 2019 at 7:15 PM [email protected]
><[email protected]> wrote:
>
>> Hi,
>> I have a Jmeter test plan where I have:
>> Thread group - OS Process Sampler - Beanshell Post Processor
>-
>> Cookie Manager
>> - HTTP Request - Summary
>>
>> The Beanshell Post Process just haas:
>> response = prev.getResponseDataAsString();
>> vars.put("SAMLResponseBody", response);
>> and the HTTP Request has in the BODY DATA:
>> ${SAMLResponseBody}
>>
>> Basically, the OS Process Sampler executes a Java app, and then the
>> Beanshell Post Processor moves the output from the Java app into a
>Jmeter
>> variable, "SampleResponseBody", and then the HTTP Request sends that
>to a
>> URL.
>> However, when I run the test plan with 100 threads with scheduler set
>for
>> 30 seconds, and I look at the Summary after the test has stopped, I
>am
>> seeing:
>> OS Process Sampler: # Samples = 106HTTP Request: # Samples = 24
>> And there are 0.00% Errors.
>>
>> I *expected* that the #Samples for the OS Process Sampler would be
>the
>> same as the #Samples for the HTTP Request, i.e., there should be one
>HTTP
>> Request for each body/string that gets produced.
>> Can someone tell me why that is not the case?
>> Thanks,Jim
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
