Abhishek Singh abhishekrsi...@gmail.com added the comment:
I found my problem.
I was also using pipes to implement my show output (between python and C). The
pipe was getting full, and xmlrpc server was locking up because of that.
The gdb traceback was confusing though (will re-open if I see
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
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
What kind of xmlrpc server do you run? And how exactly?
Try to set a timeout to all sockets:
socket.setdefaulttimeout(10)
Does this change something? Which exception (and traceback) do you get?
--
nosy: +amaury.forgeotdarc
New submission from Abhishek Singh abhishekrsi...@gmail.com:
Hi Terry,
I am running into a xmlrpc server issue where it just hangs.
9.914048127.0.0.1 - 127.0.0.1TCP 52327 8012 [SYN] Seq=0 Win=32792
Len=0 MSS=16396 TSV=3131436173 TSER=0 WS=6
00 00 00 00 00 00 00 00 00 00 00
