You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Adam McClain (JIRA)" <ji...@apache.org> on 2018/08/03 15:09:00 UTC
[jira] [Created] (HTTPCLIENT-1936) HttpClient Connections have
issues during NGINX Reloads
Adam McClain created HTTPCLIENT-1936:
----------------------------------------
Summary: HttpClient Connections have issues during NGINX Reloads
Key: HTTPCLIENT-1936
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1936
Project: HttpComponents HttpClient
Issue Type: Bug
Components: HttpClient (async)
Affects Versions: 4.5.3
Reporter: Adam McClain
We're having an issue with multiple services using HttpClient when our NGINX reverse proxy is issued a reload. We're seeing a lot of 503's, increased response times, and a lot of timeouts.
The way NGINX handles reloads, is it spins up new threads and closes the old threads once the old threads have finished responding to all of it's current traffic.
Is this a known issue? Is there a configuration setting that we could use to have the HttpClient detect that the old NGINX threads no longer exist? Is there a fix coming?
Thanks
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org