search

apache / jmeter

Apache JMeter open-source load testing tool for analyzing and measuring the performance of a variety of services
https://jmeter.apache.org/
Apache License 2.0
8.44k stars 2.11k forks source link

Non HTTP response code: java.net.SocketException,Non HTTP response message: Connection reset error from Jmeter 5.4 #5685

Open asfimport opened 2 years ago

asfimport commented 2 years ago

Chaitanya kanagala (Bug 66147): Non HTTP response code: java.net.SocketException,Non HTTP response message: Connection reset error from jmeter

I have added the following 1) user.properties : httpclient4.retrycount=1 and hc.parameters.file=hc.parameters hc.parameters : http.connection.stalecheck$Boolean=true

2) increased the port size in regedit and change client implementation to http4

3) increased the connection and response timeout in advanced tab of http sampler.

4) Added the following to jmeter properties: https.sessioncontext.shared=true https.default.protocol=TLSv1.2 https.use.cached.ssl.context=true httpclient4.retrycount=1 https.cipherSuites=TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256

But nothing worked. iam using jmeter 5.4 Can anyone please help me on this... its critical and appreciate your help.

Email:chaitu56789@gmail.com Mobile: +91-8879560349

Thanks, Chaitanya

Created attachment MicrosoftTeams-image%20%2813%29.png: Error screenshot

Error screenshot

Votes in Bugzilla: 1 Severity: normal OS: All

asfimport commented 2 years ago

@FSchumacher (migrated from Bugzilla): This seems to be a question about the usage of JMeter and thus should be asked on the users mailing list. (There are more users following the users mailing list and might be able to help, than there are developers looking into bugs)

To help you, we probably need more (different) information.

And again, this should really be discussed on the mailing list and not here!

asfimport commented 2 years ago

Chaitanya kanagala (migrated from Bugzilla): (In reply to Felix Schumacher from comment 1)

This seems to be a question about the usage of JMeter and thus should be asked on the users mailing list. (There are more users following the users mailing list and might be able to help, than there are developers looking into bugs)

To help you, we probably need more (different) information.

  • What is the simplest test plan, that doesn't work? Show that to us.
  • Are you sure, that your server is listening (with the correct protocol) on that address/port you are trying? Show an example, where you can connect with another client
  • Why did you set the parameters, that you listed above?
  • What do you mean by increased the port size in regedit? JMeter doesn't use the registry
  • (Even if I don't believe, that i will change anything) Have you tried using a current version of JMeter? (Why not?)

And again, this should really be discussed on the mailing list and not here!

I am using a test plan with multiple http requests and started a test with 10 users and error started popping up.

Yes my application is responding from browser from the machine where jmeter is facing connection reset

as i was facing the connection reset error, i tried the above parameters so that the issue resolves

regedit - i have increased the port range so that request successfully flows

we are using jmeter 5.4 as it was the stable version

asfimport commented 2 years ago

Chaitanya kanagala (migrated from Bugzilla): we can have a short meeting to sort out this issue and let me know what needs to be done from jmeter end to sort out this issue and regarding the test plan- its a UI application recorded which is successfully working fine with single user and facing this connection reset when user load is increased

asfimport commented 2 years ago

@FSchumacher (migrated from Bugzilla): (In reply to Chaitanya kanagala from comment 2)

(In reply to Felix Schumacher from comment 1) > This seems to be a question about the usage of JMeter and thus should be > asked on the users mailing list. (There are more users following the users > mailing list and might be able to help, than there are developers looking > into bugs) > > To help you, we probably need more (different) information. > > What is the simplest test plan, that doesn't work? Show that to us. > Are you sure, that your server is listening (with the correct protocol) on > that address/port you are trying? Show an example, where you can connect > with another client > Why did you set the parameters, that you listed above? > What do you mean by increased the port size in regedit? JMeter doesn't use > the registry > * (Even if I don't believe, that i will change anything) Have you tried > using a current version of JMeter? (Why not?) > > And again, this should really be discussed on the mailing list and not here!

I am using a test plan with multiple http requests and started a test with 10 users and error started popping up. Have you tried to lower the load? Less concurrent threads, less requests per seconds? Have you watched the server side? (If it was an Java server, I would do some thread dumps, or use some more advanced profiling/debugging technique)

Yes my application is responding from browser from the machine where jmeter is facing connection reset Is it responding, while the test throws errors? Is it looking slow?

as i was facing the connection reset error, i tried the above parameters so that the issue resolves

regedit - i have increased the port range so that request successfully flows Is this a special function of your server? I am not an Windows expert.

we are using jmeter 5.4 as it was the stable version Last time I looked it was 5.5 :)

And once again, please use the mailing list, as there are more helping hands, than here. https://jmeter.apache.org/mail2.html#JMeterUser

And lastly, if you need commercial support, I am sure there are IT shops, that could help you out. The support from the JMeter community is given by volunteers and by mailing list/bug tracker, only.

kmashint commented 10 months ago

We encountered this as well, with JMeter 5.6.2, and just using HttpClient4 in the Http Request Defaults didn't help, but also setting time_to_live as below in the jmeter.properties or similar user.properties file worked to avoid those errors. We set the time_to_live slightly lower than the Keep-Alive: timeout=15 (seconds) returned the service and this cleared up the errors. So there may be some lingering issue with the Keep-Alive handling in JMeter and HttpClient4. Also disabling Keep-Alive avoided the problem.

httpclient4.time_to_live=14000

laolyu commented 3 weeks ago

I also encountered the same problem. I have studied it for a long time, but I still don’t know what the reason is? v5.6.3