[mythtv-commits] Ticket #946: MySQL server gone away bug with MySQL 4.1 and 5.0

[MythTV]

#946: MySQL server gone away bug with MySQL 4.1 and 5.0
----------------------------------+-----------------------------------------
 Reporter:  d.r.newman at qub.ac.uk  |        Owner:  ijr     
     Type:  defect                |       Status:  reopened
 Priority:  major                 |    Milestone:          
Component:  mythtv                |      Version:  0.18.1  
 Severity:  medium                |   Resolution:          
----------------------------------+-----------------------------------------
Changes (by anonymous):

  * resolution:  wontfix =>
  * status:  closed => reopened

Comment:

 Hmm...

 I see this problem also. Could you explain why you don't see this as a
 mythtv bug that when a DB connection is dropped (e.g. for being idle too
 long) that mythtv doesn't successfully reconnect & needs restarting.

 Especially since there appears to be no way to tune the idle timeout for
 mysql that I can find... In fact the only place it seems to be mentioned
 on the mysql website is recommending that either the app reconnects
 successfully, or occaisonally pings the connection... Personally I see the
 reconnect being more mandatory as there are lots of things that can drop
 the connection. e.g. DB server reboot, firewall stte tables timeout etc.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/946>
MythTV <http://www.mythtv.org/>
MythTV