Sounds like it would have to be something within Witango that would kill the datasource and thread and release all related resources.
Easy for me to say. Steve -----Original Message----- From: Roland Dumas [mailto:[EMAIL PROTECTED] Sent: Friday, March 04, 2005 1:10 PM To: [email protected] Subject: Re: Witango-Talk: Baling wire and duct tape to prevent crashing Using Navicat, I monitor data connections to mysql. I can see when they go past expiry. On the 'good' server, they disappear. On the 'evil' server, they keep on going. If I kill the connection that's past expiry, one of two things happen: - witango hangs and gives error messages and I have to restart it. - the data connection is killed, but the witango thread to it stays alive, eventually crapping out witango to the point where it's eating CPU and then crashes. On 3/4/05 11:01 AM, "Fogelson, Steve" <[EMAIL PROTECTED]> wrote: > Roland, > > Wouldn't it be nice to have a cron job (or even included in Witango itself) > that would: > > Inspect datasources for their minutes idle. > Compare it to the system datasourcelife. > If it is greater, kill the datasource. > > It appears that some ODBC drivers have connection release problems. Wouldn't > this solve this particular problem? > > I have had similar problems. > > Steve Fogelson > internet Commerce Solutions ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
