[Erp5-report] r10877 - /erp5/trunk/utils/ooodoc_server/README

[nobody at svn.erp5.org]

Author: bartek
Date: Mon Oct 23 11:58:09 2006
New Revision: 10877

URL: http://svn.erp5.org?rev=10877&view=rev
Log:
added an explanation why crashed threads are locked permanently

Modified:
    erp5/trunk/utils/ooodoc_server/README

Modified: erp5/trunk/utils/ooodoc_server/README
URL: http://svn.erp5.org/erp5/trunk/utils/ooodoc_server/README?rev=10877&r1=10876&r2=10877&view=diff
==============================================================================
--- erp5/trunk/utils/ooodoc_server/README (original)
+++ erp5/trunk/utils/ooodoc_server/README Mon Oct 23 11:58:09 2006
@@ -54,4 +54,6 @@
       pids=os.popen('ps -A -o pid,ppid | grep %d | cut -f 2 -d " "' % pid)
 in pool.py.
 
+If an OOo instance crashes, it is killed and restarted after a timeout; this is ok, but the xmlrpc server thread that called that instance remains, therefore locking one client thread permanently. This is a known limitation of Python - threads can not be killed or stopped.
+
 BG