It also happens in 3.6.9, which is my prod environment. FWIW, by way of background context, this is not a heavily used app, not enough so to warrant logging to a custom buffered consumer or remote agent. It's just a small office using it. But the main home view's UI has 5 AJAX calls that cause the site to lock up on a regular basis, such that I have to have a watchdog in place to bounce Apache whenever it happens.
It's not the logging itself that's the issue; none of the AJAX views log anything. The app only actually logs maybe 100 lines per day. My investigation however turned up that if I commented out LOGGING altogether, it worked fine. Further trimming down of the codebase showed that I could remove all the loggers and it would still happen as long as any handlers were defined. So that's how I set up the demo. The logging itself isn't important, in other words; it's that the whole app is wedging just because I happen to have a vanilla LOGGING setup configured. On Thursday, April 23, 2020 at 7:02:11 AM UTC-4, Brian Tiemann wrote: > > Hi — Thanks for looking into this. Adam, I skipped over details like the > Python version because I noted them in the readme on my gitlab demo. But I > was using Python 3.7.2 for the record. > > I used "deadlock" because my digging into this had previously turned up > https://bugs.python.org/issue6721 , suggesting this was to do with thread > locking. But I'm not qualified to make that call for sure, so I don't want > to throw red herrings into the mix. If "standstill" is a better term for > this that's what I'll use. > > Thanks again. > > > On Wednesday, April 22, 2020 at 1:23:31 PM UTC-4, Brian Tiemann wrote: >> >> Hi all, >> >> I was directed here after getting corroboration on #django and elsewhere. >> >> I have what appears to be a bug in which a Django app can deadlock if you >> hit it with a lot (>3) of AJAX requests within a short time (i.e. all >> triggered in parallel from a single HTML page). I have a reproducible case >> here: >> >> https://github.com/data-graham/wedge >> >> I'd really appreciate it if someone could take a look and let me know >> whether I'm doing something wrong, or if there's something systemic going >> on. Thanks much! >> >> -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9a5bc078-66b9-4e09-97c2-8340b8882c02%40googlegroups.com.
