Abhishek Singh <abhishekrsi...@gmail.com> added the comment: I have a pretty complicated setup. 100's of threads, xmlrpc being in the main thread and providing show routines for my program. I have 10's of such processes doing some heavy duty simulation/crunching.
The threads and program is in C. I use swig routines to throw in my show framework. There is no traceback - it is just stuck and unresponsive. If I quit my client, the socket gets closed and it recovers. But it is annoying to do so, and it can get stuck again :(. I will try your timeout suggestion, but having a infinite timeout might help given my system is loaded with lots of competing (for CPU) threads. I am running the Simple xmlrpc server. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15021> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
