Message162560
| Author |
Abhishek.Singh |
| Recipients |
Abhishek.Singh, amaury.forgeotdarc |
| Date |
2012年06月09日.13:21:45 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1339248107.86.0.107131220166.issue15021@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年06月09日 13:21:48 | Abhishek.Singh | set | recipients:
+ Abhishek.Singh, amaury.forgeotdarc |
| 2012年06月09日 13:21:47 | Abhishek.Singh | set | messageid: <1339248107.86.0.107131220166.issue15021@psf.upfronthosting.co.za> |
| 2012年06月09日 13:21:47 | Abhishek.Singh | link | issue15021 messages |
| 2012年06月09日 13:21:45 | Abhishek.Singh | create |
|