One more symptom: in my scheme to keep all the datasources alive forever by hitting them periodically, one thing fails. Eventually, even though there are no expiry hangs, witango's CPU usage climbs to the point of pegging it and making the system slow to a crawl.
I've got a developer trying to create an install of the most recent odbc drivers, but he's hung up on compiler errors. We'll have to schedule an OS upgrade, which is a big disruptive deal. (still perplexed why 2 identical installs on identical machines turn out so differently) On 3/4/05 11:09 AM, "Roland Dumas" <[EMAIL PROTECTED]> wrote: > 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. > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
