Webware itself seems totally stable. However, you are always at the mercy of whatever C-coded extension libraries you are using. One bug there and either your whole process goes down, or your threads get wedged one at a time until there are no threads left available to handle requests. That's the advantage of a multi-process model -- an unstable extension library is much less harmful.
FWIW, I still have some code sitting around that can cause a process to kill itself even when there are stuck threads: http://svn.colorstudy.com/home/ianb/thread_die.py
If someone wanted to monitor thread health, you could use this to restart the process (by exiting with a known error code, e.g. 3, and starting the app with a script that monitors the exit code and restarts if necessary; i.e., the same thing AutoReload does). Since the most common problem is wedged threads (rather than the entire process segfaulting, or the entire process becoming wedged), this would handle that situation.
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
