Hi Ameisen,,
How did you resolve this issue? I am facing same issue with FastCGI application too.
It accepts
> connections on the listener socket, and defers them to other threads
> to process (which do so using a fiber pool) while the listener thread
> keeps listening for more connections.
This is how many network applications does accept concurrent requests by doing multiplexing which is fundamental of network programming. I am too surprised that nginx not allowing its backend applications to do that.
How did you resolve this issue? I am facing same issue with FastCGI application too.
It accepts
> connections on the listener socket, and defers them to other threads
> to process (which do so using a fiber pool) while the listener thread
> keeps listening for more connections.
This is how many network applications does accept concurrent requests by doing multiplexing which is fundamental of network programming. I am too surprised that nginx not allowing its backend applications to do that.