#31373: Django 3.x / uwsgi is leaking connections
-------------------------------------+-------------------------------------
Reporter: Marcin Nowak | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Andrew Godwin):
That would not surprise me - next things to investigate are:
- Of course, reverting that one change and seeing if it fixes it.
- Does uwsgi override any part of the threading module? This happens with
gevent and, I think, mod_wsgi, and it causes havoc as they ruin thread
IDs.
- Checking a couple of recent major versions of asgiref within Django's
compatibility range, to see if the change was there (doubtful)
Likely cause is that the close_old_connections() task is never being run
in what Local thinks is the same thread as before. I have a potential
workaround we can do if it _is_ overriding thread IDs, but if not, we'll
have to dive deeper and see what we can fix about it.
--
Ticket URL: <https://code.djangoproject.com/ticket/31373#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.7b0b28c32f418fc4c208eb9241b446d2%40djangoproject.com.
