Hi Maxim, We have tried different settings with 'lingering_close always;' and 'lingering_time', 'lingering_timeout' up to 240s with no success. Would you be able to confirm whether it is an nginx problem in the lingering close automatic logic as you mentioned if I provide an example to reproduce it? Thanks, Dario Maxim Dounin Wrote: -----------------------------------------------by nginxuser2018 - Nginx Mailing List - English
One setting that I noticed mitigates the problem is to use `lingering_close always;` however in our infrastructure this can lead to the build up of worker processes (for the duration of the lingering_timeout). What are the advantages and drawbacks of using this setting?by nginxuser2018 - Nginx Mailing List - English
I noticed that if I setup a simple scenario where a client is making concurrent requests on a server with nginx configured as a reverse proxy and SSL traffic termination endpoint, if I trigger a reload with 'nginx -s reload' mid requests, often times the client will throw an 'javax.net.ssl.SSLException: SSLEngine closed already at io.netty.handler.ssl.SslHandler.wrap(...)(Unknown Source)' exceptby nginxuser2018 - Nginx Mailing List - English