On Tue, Nov 19, 2019 at 09:48:23PM -0500, wu560130911 wrote:
Hi there,
> when use Nginx version before the version of 1.15.3, Nginx can't know when
> tomcat will be close connection, so online have 502 error;
> I have adjust the size of keepAliveTimeout, but the problem still occur,
> because us
I'm use Nginx proxy to tomcat, tomcat have two parameters manage keep
alive, first one is keepAliveTimeout : how the connection idle time; second
is maxKeepAliveRequests : how the connection reuse counts;
when use Nginx version before the version of 1.15.3, Nginx can't know when
tomcat will be cl
Hello!
On Mon, Feb 25, 2019 at 09:46:56PM +0800, yf chu wrote:
> But if a connection to upstream is dead or there are some other
> network problems in this connection, how could Nginx handle it,
> will the HTTP requests on this connection be affected? For
> example, is it possible that the HTT
But if a connection to upstream is dead or there are some other network
problems in this connection, how could Nginx handle it, will the HTTP requests
on this connection be affected? For example, is it possible that the HTTP
requests on this connection is hanging until timeout?
At 2019
Hello!
On Mon, Feb 25, 2019 at 03:45:27PM +0800, yf chu wrote:
> The Nginx document said that there are two upstream-related
> directives introduced in the version of 1.15.3:
> "keepalive_requests" and "keepalive_timeout". But the directive
> "keepalive" has already been instroduced in the v
The Nginx document said that there are two upstream-related directives
introduced in the version of 1.15.3: "keepalive_requests" and
"keepalive_timeout". But the directive "keepalive" has already been
instroduced in the version of 1.1.4. So I want to know how does Nginx handle
the keepalive c
