Yeah it's possible for the channel / socket to close (client hangup, channel
timeout, etc) while the WSGI app is still processing the request. The WSGI
execution thread will have no idea until it tries to actually write the
response at which point an exception may be raised but this is usually
Thanks both Michael and Bert for explanation. process x thread
Yes the documentation confuse me a little bit specially this sentence in
channel_timeout docs.
"Inactive" is defined as "has received no data from a client and has
sent no data to a client".
Best regards Michal
On 5/20/20 10:06
Hey Michal,
Unfortunately there is nothing that will cause Waitress to kill a thread,
because killing a thread in Python is not possible. The channel_timeout refers
to how long a keep-alive connection stays open, a request that is processing in
the WSGI thread will still be considered open,
Waitress is a threaded WSGI server and there isn't a safe way to kill threads
inside of a process while they are blocked executing synchronous code. Even if
the underlying channel is closed, the thread continues until the request is
completed processing and then the response is simply discarded
Hello,
I can not figure out how to setup timeout (request processing takes to much
time) and size limit for output data.
I am starting server like this:
serve(application,
host='0.0.0.0',
port=port,
cleanup_interval=2,
channel_timeout=4
)
I am
Hello,
I can not figure out how to setup timeout (request processing takes to much
time) and limit for output data.
I am starting server like this.
serve(application,
host='0.0.0.0',
port=port,
cleanup_interval=2,
channel_timeout=4
)
I am using
