#31515: Django tries to reuse MySQL connections that have gone away with ASGI
-------------------------------------+-------------------------------------
Reporter: Braunson | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Braunson):
Replying to [comment:3 Simon Charette]:
> You don't have to be explicitly using asgiref to be affected by the
issue; Django uses it internally to keep reference to database connections
and other globals.
>
> Could you try upgrading to `asgiref>=3.2.7` and see if it helps? Prior
version had a bug which showed similar symptoms in #31373.
Unfortunately that requirement did not help. After a few hours of
operation the error continues to appear again. So even with the max age
set to 0 it keeps trying to reuse those old database connections long
after the server terminates them.
--
Ticket URL: <https://code.djangoproject.com/ticket/31515#comment:4>
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/067.c4a3640a9287349db608280a6b02ee1d%40djangoproject.com.
