I can't speak for the MySQL module, but when using the DCOracle2 module, database connections are automatically and reliably closed when the app server is stopped or restarted.
Cheers! -- David Hancock | [EMAIL PROTECTED] | 410-266-4384 -----Original Message----- From: Costas Malamas [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 11:48 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Webware-discuss] More trouble with DBPool... That creates another question in my head: If connections are created as instance variables for a servlet, when are they close()'d ? I thought that MySQL automatically closed connections if the python module exited, but now I aint so sure anymore... Costas >From: "Aaron Held" <[EMAIL PROTECTED]> >To: "Costas Malamas" <[EMAIL PROTECTED]>, ><[EMAIL PROTECTED]> >Subject: Re: [Webware-discuss] More trouble with DBPool... >Date: Mon, 6 May 2002 22:30:40 -0400 > >If you are using store multiple times in a page it may be opening >connections faster then closing them. I know that MySQL is very quick >to setup a new connection, but I have no idea how it is closing them. > >I have also had issues with DBPool where connections seemed to be left >open after calling the close function, but I could never track it down >and it went away with some rewriting of the startup code. > >-Aaron >----- Original Message ----- >From: "Costas Malamas" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Monday, May 06, 2002 6:19 PM >Subject: [Webware-discuss] More trouble with DBPool... > > > > Expanding the recent discussion on DBPool, I tried to implement >this on my > > site (http://memigo.com/) which does a lot of very heavy MySQL >lifting > > --thus I need all the DB speed-up DBPool can give. DBPool >seemed to be > > saturating the MySQL daemon and I had to go back to the old >config. > > > > Let me see if I can explain what's happening. The various page >classes > > include an instance variable (or >1), self.store that itself is >an instance > > of a Store class. I have two versions of Store: > > > > Version 1 instantiates a single connection in the Store.py >module and passes > > it to Store and its subclasses: > > (Store.py:) > > _conx = MySQLdb.Connection(...) > > > > class Store: > > def __init__(self): > > self.conx = _conx > > > > Version 2 creates a DBPool at the module level and then Store >asks for a > > connection: > > (Store.py:) > > dbPool = DBPool.DBPool(...) > > > > class Store: > > def __init__(self): > > self.conx = dbPool.getConnection() > > > > Now, V.1 is what I used to have and it worked fine (but slowly) >most of the > > time, except under very heavy loads. Trying to help the heavly >load > > situation, I implemented V.2 instead. However, after a short >little test > > drive, V.2 was flooding MySQL (I kept getting "Too many >connections" > > errors). > > > > Any ideas? I have to admit that the DBPool situation is >confusing me... > > > > Thanks, > > > > Costas > > > > > > > > >_________________________________________________________________ > > MSN Photos is the easiest way to share and print your photos: > > http://photos.msn.com/support/worldwide.aspx > > > > > > _______________________________________________________________ > > > > Have big pipes? SourceForge.net is looking for download >mirrors. We supply > > the hardware. You get the recognition. Email Us: >[EMAIL PROTECTED] > > _______________________________________________ > > Webware-discuss mailing list [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/webware-discuss > > > > >_______________________________________________________________ > >Have big pipes? SourceForge.net is looking for download mirrors. We >supply the hardware. You get the recognition. Email Us: >[EMAIL PROTECTED] >_______________________________________________ >Webware-discuss mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/webware-discuss _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
