openlp-core team mailing list archive

[Raoul Snyman <raoul.snyman@xxxxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: openlp
     Importance: Medium
     Assignee: Raoul Snyman (raoul-snyman)
         Status: New

** Changed in: openlp
     Assignee: (unassigned) => Raoul Snyman (raoul-snyman)

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/927473

Title:
  MySQL server has gone away

Status in OpenLP - Worship Presentation Software:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/927473/+subscriptions