> Most of these ideas could be implemented, but they aren't there > currently. The one thing I don't see how we could do would > be to stop > threads that are taking too long. I think there's no way to > kill a running > thread in Python, at least not portably. (And even if you > could do so, it > would leave the whole process in an unstable state. The docs > on the Win32 > functions for killing threads warn you to do it only as a > last resort as it > makes the whole process unstable; I assume similar warnings > apply for Unix.)
I was afraid of that. I'm coming from Cold Fusion where you could specify how long a page could take to respond. Not a big deal, was just wondering. > The best we could do is monitor the health of threads, and if > threads are > dying or getting stuck in infinite loops, we could do an "emergency > shutdown" where we wait some length of time for the currently > processing > threads to exit, but if they don't exit in some time period, > then we just > try to pickle the sessions to disk and exit the process. Then some > watchdog process would notice that WebKit had stopped and restart it. > > Of course, it's even better to just eliminate all bugs in > WebKit and in > your servlets so that threads never die or get in infinite > loops :-) Are > you actually noticing that threads are getting wedged? The cookie problem was killing off my threads but thats fixed now. I don't know what other things could cause threads to die, maybe syntax errors? Now that I have a live server, I get nervous and wonder if the threads are all healthy but I can't think of a way to check them. Maybe the admin area could have a thread status page. Jeff _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
