python - Flask / Werkzeug - sockets stuck in CLOSE_WAIT -


i've run situation api built on flask-restul intermittently becomes non-responsive. it's running werkzeug (which i'm aware non-production use only) , single threaded. complicate things little further wrapped inside axscript within application.

when non-responsive, significant number of sockets show in close_wait there's not being handled correctly during client initiated socket teardown.

as running single threaded appears internals of request handler may blocking indefinitely preventing other requests being accepted , causing client timeout. however, thread busy prevents socket closing.

does sounds sane assumption based on knowledge other have of framework? also, if unhanded exception thrown within request handler, result in 500 error being returned, or there other scenario here i'm missing?


Comments

Popular posts from this blog

user interface - how to replace an ongoing process of image capture from another process call over the same ImageLabel in python's GUI TKinter -

javascript - Restarting Supervisor and effect on FlaskSocketIO -

php - Mongodb connectivity error -