Discussion:
Jmeter error : Non HTTP response code
mahesh bhasme
2016-10-27 04:36:40 UTC
Permalink
Hi ,
we have jmeter request which hit to tomcat server and which required aorunf
30 minutes to process by server, When we hit request to server, jmeter get
timeout after 300 sec and throws below error. It dont wait till get response

*SamplerError-Response code: Non HTTP response code:
java.net.SocketException Response message: Non HTTP response message:
socket closed
*

To solve above error applied below solution in jmeter

1. Changed "Implementation" of your HTTP Requests to HTTPClient4
2. Added below parameters in user.properties
httpclient4.retrycount=1
hc.parameters.file=hc.parameters
3. added below parameter in hc.parameters
http.connection.stalecheck$Boolean=true
https://wiki.apache.org/jmeter/JMeterSocketClosed


Note: same request is running fine in POSTMAN, no timeout error.

Could you please help ?
--
Thanks,
MAhesh
Bo Bodnar
2016-10-27 14:14:08 UTC
Permalink
I've seen this problem before. The destination's overloaded and is
rejecting traffic. Retrying the request may solve the problem, but I'd be
curious as to why the destination's overloaded (excessive GC? DB
overloaded? etc.).

Best regards,

Bo




Bohdan L. Bodnar
Lead Performance Engineer
1-312-871-5163




E-mail: ***@us.ibm.com 222 South Riverside Plaza
Chicago, IL 60606
United States






From: mahesh bhasme <***@gmail.com>
To: JMeter Users List <***@jmeter.apache.org>
Date: 10/26/2016 11:36 PM
Subject: Jmeter error : Non HTTP response code



Hi ,
we have jmeter request which hit to tomcat server and which required aorunf
30 minutes to process by server, When we hit request to server, jmeter get
timeout after 300 sec and throws below error. It dont wait till get
response

*SamplerError-Response code: Non HTTP response code:
java.net.SocketException Response message: Non HTTP response message:
socket closed
*

To solve above error applied below solution in jmeter

1. Changed "Implementation" of your HTTP Requests to HTTPClient4
2. Added below parameters in user.properties
httpclient4.retrycount=1
hc.parameters.file=hc.parameters
3. added below parameter in hc.parameters
http.connection.stalecheck$Boolean=true
https://wiki.apache.org/jmeter/JMeterSocketClosed


Note: same request is running fine in POSTMAN, no timeout error.

Could you please help ?
--
Thanks,
MAhesh
mahesh bhasme
2016-10-27 14:21:35 UTC
Permalink
Destination server is busy with some processing and DB response, it takes
time about 35 min to responsd, however in this case Jmeter should not
timeout and this is not happening with POSTMAN. Also tried Jmeter's https
request's Response timeout paramter but it not helped. any other
config/solution ?

Thanks,
Mahesh
I've seen this problem before. The destination's overloaded and is
rejecting traffic. Retrying the request may solve the problem, but I'd be
curious as to why the destination's overloaded (excessive GC? DB
overloaded? etc.).
Best regards,
Bo
*Bohdan L. Bodnar*
Lead Performance Engineer
1-312-871-5163
------------------------------
222 South Riverside Plaza
Chicago, IL 60606
United States
[image: Inactive hide details for mahesh bhasme ---10/26/2016 11:36:57
PM---Hi , we have jmeter request which hit to tomcat server and]mahesh
bhasme ---10/26/2016 11:36:57 PM---Hi , we have jmeter request which hit to
tomcat server and which required aorunf
Date: 10/26/2016 11:36 PM
Subject: Jmeter error : Non HTTP response code
------------------------------
Hi ,
we have jmeter request which hit to tomcat server and which required aorunf
30 minutes to process by server, When we hit request to server, jmeter get
timeout after 300 sec and throws below error. It dont wait till get response
socket closed
*
To solve above error applied below solution in jmeter
1. Changed "Implementation" of your HTTP Requests to HTTPClient4
2. Added below parameters in user.properties
httpclient4.retrycount=1
hc.parameters.file=hc.parameters
3. added below parameter in hc.parameters
http.connection.stalecheck$Boolean=true
https://wiki.apache.org/jmeter/JMeterSocketClosed
Note: same request is running fine in POSTMAN, no timeout error.
Could you please help ?
--
Thanks,
MAhesh
--
Thanks,
MAhesh
Deepak Shetty
2016-10-28 18:33:55 UTC
Permalink
Hi
have you changed any of the default timeout properties in jmeter.properties
(or equivalent) and/or hc.parameters? Did you try setting a larger timeout
value on the sampler itself ?
Post by mahesh bhasme
Destination server is busy with some processing and DB response, it takes
time about 35 min to responsd, however in this case Jmeter should not
timeout and this is not happening with POSTMAN. Also tried Jmeter's https
request's Response timeout paramter but it not helped. any other
config/solution ?
Thanks,
Mahesh
I've seen this problem before. The destination's overloaded and is
rejecting traffic. Retrying the request may solve the problem, but I'd be
curious as to why the destination's overloaded (excessive GC? DB
overloaded? etc.).
Best regards,
Bo
*Bohdan L. Bodnar*
Lead Performance Engineer
1-312-871-5163
------------------------------
222 South Riverside Plaza
Chicago, IL 60606
United States
[image: Inactive hide details for mahesh bhasme ---10/26/2016 11:36:57
PM---Hi , we have jmeter request which hit to tomcat server and]mahesh
bhasme ---10/26/2016 11:36:57 PM---Hi , we have jmeter request which hit
to
tomcat server and which required aorunf
Date: 10/26/2016 11:36 PM
Subject: Jmeter error : Non HTTP response code
------------------------------
Hi ,
we have jmeter request which hit to tomcat server and which required
aorunf
30 minutes to process by server, When we hit request to server, jmeter
get
timeout after 300 sec and throws below error. It dont wait till get response
socket closed
*
To solve above error applied below solution in jmeter
1. Changed "Implementation" of your HTTP Requests to HTTPClient4
2. Added below parameters in user.properties
httpclient4.retrycount=1
hc.parameters.file=hc.parameters
3. added below parameter in hc.parameters
http.connection.stalecheck$Boolean=true
https://wiki.apache.org/jmeter/JMeterSocketClosed
Note: same request is running fine in POSTMAN, no timeout error.
Could you please help ?
--
Thanks,
MAhesh
--
Thanks,
MAhesh
Loading...