I would start in the log and make sure each START statement has an END, if not, at least you know where to look. Also check witanogevents.log for anything strange.
-----Original Message----- From: John McGowan [mailto:[EMAIL PROTECTED] Sent: Thursday, April 13, 2006 4:07 PM To: [email protected] Subject: Witango-Talk: What goes up... Must Come Down I just moved a site to my 5.5 server and I'm seeing the server become unresponsive after a while. ActiveQryThr gradually grows to the max, and then the server doesn't respond. I thought it was just because my query timeout was set too high (it was at 5 minutes, I have some admin tasks that can take a long time time to execute) However, I changed the query timeout to 30 seconds, and I'm still seeing the number of threads climb to 20 and then the server craps out. Anybody ever run into this... If something is taking too long, it should be easy to detect through the Witango log, right? /John ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
