JMeter Error: Nohttpresponseexception

Colleague performance test encountered random errors, but must now, jmeter error "nohttpresponseexception:the target server failed to respond."

The answer is in this link: https://wiki.apache.org/jmeter/JMeterSocketClosed

The text says:

Retry or stale check can hide issues Onserver configuration:

· Server failing to send the (optional) keep-alive header

· Overwhelmed server refusing connection, retrying would increaseload

My understanding is: the lower version (2.10 or less) JMeter will hide the above two server-side problems, so the high version JMeter canceled the original settings, so that the two errors can be exposed.

The analysis of the HTTP header reveals that the colleague's test encountered exactly the first case: the server did not return the keep-alive header.

Why the server did not return, this need to check the data, look at the Tomcat configuration or view code (tomcat should be enabled by default can be returned).

In order to avoid the JMeter report this error, there are several ways to try it out:

1) JMeter request is set to not need keep-alive;

2) JMeter settings revert to the old version of the settings, that will be re-connected, and stale check, according to the information found, said the browser is actually enabled this setting;

3) Use a temporary setting for the new version of JMeter: Httpclient4.idletimeout; (2.12)

(the latter two are mentioned in the above link)

As for detailed analysis, there is no time for continuous monitoring, packet capture, testing and analysis. Make a note of soy sauce.