OK, I didn't actually figure out how to kill wedged threads, but I did figure out how to (more or less) cleanly exit the process when there's wedged threads. The code is in http://svn.colorstudy.com/home/ianb/thread_die.py -- mostly it calls os._exit, which exits unconditionally, and it has some guards so that it tries to exit as cleanly as possible.

We still don't detect wedged threads, but at least this gives us something to do if we did detect those threads. It probably wouldn't be hard to add to ThreadedAppServer -- though there's some added infrastructure to figure out what to do when you do find a wedged thread. E.g., maybe it should just send an email, or it should exit (code 3), or do both.

--
Ian Bicking  /  [EMAIL PROTECTED]  /  http://blog.ianbicking.org


------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to