> >> Hi, Roberto, Jacob, >> >> actually considering the percent of these errors is very low (after >> decreasing the timeout), and the fact that the browser reconnects >> immediately, lowers the priority of this problem significantly. >> >> Though even if there's a long-blocking piece somewhere in the >> application >> code, I don't know of it, and it seems it's extremely hard to track >> down. >> >> Jacob, the difference with your case is that this happens simultaneously >> for several (but not all!) clients. > > > Hi, i think that the highest priority (now) is giving better infos in the > error (at least the REMOTE_ADDR and the REQUEST_URI vars) > > I should be able to push a patch in the next few minutes
here it is: https://github.com/unbit/uwsgi/commit/6699f4046e27ea84b06ee91eb312676b8228392a -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
