My system allows users to write their own python code fragments for some 
tasks.  Unfortunately the users sometimes write infinite loops, which 
gradually lock up threads until none remain.  A few minutes later a 
monitor notices that the system is unresponsive and kills and restarts 
AppServer.  There must be a better way.

1. Can I find out how long each busy thread has been working on its 
current request?
2. Can I kill threads without irritating w4py?

I guess I can roll my own solution for detecting busy threads, but I'm 
hoping someone else has a solution for this, or that I've failed to 
notice something obvious that already exists.


   Oliver


_______________________________________________
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to