#31515: Django tries to reuse MySQL connections that have gone away with ASGI
-------------------------------------+-------------------------------------
Reporter: Braunson | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: 3.0
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
This bug only appears to happen when using ASGI. No matter the
`CONN_MAX_AGE` it seems to be ignored. I have tried both manually setting
to 0 so they are never reused and setting them to an hour without any
effect.
If it makes a difference I am using multiple databases. Again this issue
does NOT occur with WSGI, only with ASGI.
Is there any work around I can do to solve this in the meantime? It
results in almost every page 500 erroring once or twice and a refresh
fixes it temporarily for the client.
--
Ticket URL: <https://code.djangoproject.com/ticket/31515>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.eaeb4b771bfeb540d9febc287aac234e%40djangoproject.com.
