On 12/26/06, Roger Haase <[EMAIL PROTECTED]> wrote: > Hi, > > I am testing a new server with Fedora Core 6 and Middlekit-Webware 9.2 > and MySQL 5.0. When the new server is idle for 5 (or more) hours I get > abends with OperationalError: (2006, 'MySQL server has gone away'). > Restarting the webkit AppServer eliminates the immediate problem. > > I have not seen this problem on a lightly loaded server with Fedora > Core 4, MySQL 4.1, and Webware 9.1. The Webkit AppServer is restarted > by cron daily in both cases. In both cases the result of a call to > Middlekit MySQLObjectStore is saved in the Sitepage module at load time > for use by all servlets. > > Where should I be setting a timeout parameter for the Middlekit-MySql > connection? Is 24 hours an unreasonable time limit?
Did your version of MySQLdb change as well? I've had problems on more than one occasion when upgrading. Also, is there a setting on the server side, perhaps? Maybe something about how long to keep connections alive? If this ultimately requires a fix in MiddleKit, I'm not yet sure what it should be or where it should go, as I haven't experienced this problem myself (but have not yet run MySQL 5 for lengthy periods of time). One option you might try is tweaking MiddleKit\Run\MySQLObjectStore.py to trap that specific exception and do some kind of recovery and retry. If you need help coding that, let me know. But if there is a MySQL option that applies, that will be probably be the most expedient fix. Let us know how it goes, -Chuck ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss