[
https://issues.apache.org/jira/browse/HTTPCLIENT-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1936.
-------------------------------------------
Resolution: Incomplete
It is unclear how the issue is related to HttpClient and it is we are expected
to do. Please also consider upgrading to HttpClient 5.
> 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
> Priority: Major
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
