I've also seen the issue when running plain nginx 1.9.11 sort like builting
a new nginx, only the issue is that upstream closes cnxs, not nginx.
Since I've discovered that our TCs had the Connector' keepAliveTimeout way
low (10 msec), mistakenly thought the units were sec and not as actually
msec.
stefws Wrote:
---
> Seems I'm not alone w/TC issues ;)
missed the link:
http://permalink.gmane.org/gmane.comp.web.haproxy/26860
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265031,265079#ms
Seems I'm not alone w/TC issues ;)
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265031,265078#msg-265078
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
@B.R. You're right, seemed my upstream tomcat instances were RESETing cnx as
reply something.
So far I improved it a lot my altering a http connector keepAliveTimeout
value from mistakenly expressed as sec when in fact it should be msec ;)
When heavy load it still occurs but far less frequently,
My config btw:
user imail;
worker_processes auto;
daemon on;
master_process on;
error_log logs/mos_error.tcp debug_tcp;
error_log logs/mos_error.log;
pid/opt/imail/nginx/logs/mos_nginx.pid;
worker_rlimit_nofile 20;
worker_rlimit_core 500M;
working_directory /opt/imail/nginx;
e
