This is an EXCEPTION caused by HTTP and is an accidental exception.

Abnormal log

org.apache.http.NoHttpResponseException: The target server failed to respond
Copy the code

The solution

Server solution

The client can detect that the service has expired and shut it down.

  • Keep-alive: timeout=xx (HttpHeader); keep-alive: timeout=xx (HttpHeader);
  • The second parameter in the Nginx configuration is this, so as long as the server keeps alive_timeout 30s; Keepalive_timeout 30s 29s; Ok, less 1s here to prevent concurrency problems caused by network delay.

Client solution

If the server is not convenient to modify, then the second solution is to modify the client side, more troublesome.

  • First, make sure you use the latest oneshttpClient.
  • Secondly, there are three ways:
    1. forjestThis type has timingcloseIdleConnection, the scheduling time can be adjusted askeep aliveLess than half the time to ensure recycling before timeout
    2. According to thekeep AliveTime, adjustmentValidateAfterInactivity less thanKeepAlive Time ‘, but this method still does not avoid simultaneous closing.
    3. Compensation scheme, useRetryRetry sending.HttpClientAuto retry is enabled by default, do not calldisableAutomaticRetriesCan be

Recommended scheme

  1. The client uses a short connection, such as aUrlConnection;
  2. willHttpClientThe connection keepalive time is set to less than 15 seconds or lessnginx 的 keepalive_timeoutTune more than 30s;
  3. Don’t have toPoolingHttpClientConnectionManager;
  4. Retry after error,HttpClient 的 RetryHandler;
  5. JDK11 has been broughtHttpClinetIsn’t that attractive?