Re: SSLEngine closed already exception triggered by reload

2018-11-09 Thread nginxuser2018
rovide an example to reproduce it? Thanks, Dario Maxim Dounin Wrote: --- > Hello! > > On Mon, Nov 05, 2018 at 09:14:33AM -0500, nginxuser2018 wrote: > > > I noticed that if I setup a simple scenario where a client is makin

Re: SSLEngine closed already exception triggered by reload

2018-11-06 Thread nginxuser2018
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? Posted at Nginx Forum: ht

SSLEngine closed already exception triggered by reload

2018-11-05 Thread nginxuser2018
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.SSLExce