I would suspect that there are threads locked up. Some external actions (command lines, @URL) can lock up a thread if they fail to complete properly.
You can see you active thread count in @serverstatus, if it's great than 1, then you may have a thread that can't shutdown (of course it could also be a valid processing request). You can safely 'net stop' the service and then 'kill' the service if that doesn't work. I have not found that full restarts of the server are ever necessary. If this is happening more than rarely, I would try to monitor the thread count throughout the day, as this is probably something that can be avoided. Oh and if you look in the Witango log, you should see the thread counter never dropping back down to 1 once a thread gets locked up. I have never experienced another reason for a service to not properly shutdown. Robert _____ From: Ted Wolfley [mailto:[email protected]] Sent: Tuesday, January 27, 2009 8:11 AM To: [email protected] Subject: Witango-Talk: witango 5.5 restart Hi, I have a crontab on a Windows 2003 server that restarts the Witango service every morning at 12 am. Occasionally the Witango service hangs while shutting down and I have to restart the server. I'm thinking the cause is the open connections to Witango and Witango is trying to close them. Is there a way to drop all the connections before restarting the Witango service? Ted Wolfley Lead Internet and Database Programmer The Ogden Group of Rochester phone: (585) 321 1060 x23 fax: (585) 321 0043 <mailto:[email protected]> [email protected] <http://www.ogdengroup.com> www.ogdengroup.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
