#34389: Django not closing database connections on ASGI application after an
upgrade to 4.1
-------------------------------+--------------------------------------
Reporter: vsobotka | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 4.1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => needsinfo
Comment:
Thanks for the report. ​Django has a
[https://github.com/django/django/blob/b05dfc289429dc4de990617da543af681d6638c7/django/db/__init__.py#L53-L61
routine] to clean up old connections that is tied into the request-
response life-cycle, so idle connections should be closed. However, I
don't think you've explained the issue in enough detail to confirm a bug
in Django. This can be an issue in `psycopg2`, `uvicorn`, or in custom
middlewares (see #31905) it's hard to say without a sample project.
Please reopen the ticket if you can debug your issue and provide details
about why and where Django is at fault, or if you can provide a sample
project with reproducible scenario.
See also #33497 and #31134 for potential duplicates.
--
Ticket URL: <https://code.djangoproject.com/ticket/34389#comment:1>
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/01070186b6485000-0a91c64f-a1d8-4788-ab5b-fcdcf9607fbc-000000%40eu-central-1.amazonses.com.
