#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout
passed
-------------------------------------+-------------------------------------
Reporter: ekeydar@… | Owner: aaugustin
Type: Bug | Status: closed
Component: Database layer | Version: 1.6
(models, ORM) | Resolution: wontfix
Severity: Release blocker | Triage Stage: Accepted
Keywords: mysql | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: assigned => closed
* resolution: => wontfix
Comment:
Actually this is the intended behavior after #15119. See that ticket for
the rationale.
----
**If you hit this problem and don't want to understand what's going on,
don't reopen this ticket, just do this:**
- **RECOMMENDED SOLUTION: close the connection with `from django.db import
connection; connection.close()` when you know that your program is going
to be idle for a long time.**
- ''CRAPPY SOLUTION: increase wait_timeout so it's longer than the maximum
idle time of your program.''
In this context, idle time is the time between two successive database
queries.
--
Ticket URL: <https://code.djangoproject.com/ticket/21597#comment:29>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/075.18c5d1cdaec19f029fdca8a2806ac18b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
