I see. so in this case the request was completely sent in single write
without blocking that there is no need to schedule a write timer anymore,
otherwise it is necessary.
Thanks for the explanations!
b.t.w, have you ever seen the work process is listening on the socket?
Posted at Nginx Forum:
On Fri, Apr 12, 2019 at 09:21:07PM -0400, allenhe wrote:
> I understand the connection establish timer, write timer and read timer
> should be setup and removed in order, but where is the write timer?
It's not that simple. Writing and reading are done in parallel.
In fact if nginx receives the r
I understand the connection establish timer, write timer and read timer
should be setup and removed in order, but where is the write timer? are
there lines in the logs saying I'm going to send the bytes, the sending is
on-going, and the bytes has been sent out?
Posted at Nginx Forum:
https://foru
On Fri, Apr 12, 2019 at 08:51:05AM -0400, allenhe wrote:
> but it looks to me the timer was set for the write not the read,
If the request is sent and the response is not yet received, nginx schedules a
timer for proxy_read_timeout.
> also the
> subsequent message isn't telling the nginx was int
but it looks to me the timer was set for the write not the read, also the
subsequent message isn't telling the nginx was interrupted while sending the
request?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,283735,283739#msg-283739
___
nginx
Hello Allen,
On Fri, Apr 12, 2019 at 06:01:14AM -0400, allenhe wrote:
> Hi,
>
> The Nginx hangs at proxying request body to the upstream server but with no
> error indicating what's happening until the client close the font-end
> connection. can somebody here help give me any clue? following is t
Hi,
The Nginx hangs at proxying request body to the upstream server but with no
error indicating what's happening until the client close the font-end
connection. can somebody here help give me any clue? following is the debug
log snippet:
2019/04/12 14:49:38 [debug] 92#92: *405 epoll add connecti
