MySQL server has gone away
Bug #927473 reported by
Raoul Snyman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenLP |
Fix Released
|
Medium
|
Raoul Snyman | ||
Bug Description
When using MySQL, if connections have been open longer than an hour, MySQL closes the connection but does not inform the application. This results in the following error message:
OperationalError: 2006, 'MySQL server has gone away'
The easiest way to fix this is most likely to use the NullPool class in SQLAlchemy when creating the connection. This will force SQLAlchemy to create a new connection every time, bypassing this issue.
Related branches
lp:~raoul-snyman/openlp/bug-927473
- Tim Bentley: Approve
- Jon Tibble: Pending requested
-
Diff: 149 lines (+83/-6)1 file modifiedopenlp/core/lib/db.py (+83/-6)
| Changed in openlp: | |
| assignee: | nobody → Raoul Snyman (raoul-snyman) |
Revision history for this message
| Raoul Snyman (raoul-snyman) wrote | #1 |
Revision history for this message
| mahfiaz (mahfiaz) wrote | #2 |
Revision history for this message
| Raoul Snyman (raoul-snyman) wrote | #3 |
| Changed in openlp: | |
| status: | New → Fix Committed |
| Changed in openlp: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Phill (phill-ridout) wrote | #4 |
Revision history for this message
| Raoul Snyman (raoul-snyman) wrote | #5 |
To post a comment you must log in.
It looks like we're already using NullPool. There goes that theory...