Issue 9851: multiprocessing socket timeout will break client (original) (raw)

Issue9851

Created on 2010-09-14 08:28 by hume, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (5)
msg116375 - (view)	Author: hume (hume)	Date: 2010-09-14 08:28
when use multiprocessing managers, while use socket to communicate between server process and client process, if I used the global socket timeout feature(no matter how large the value is) the client will always say File "c:\python27\lib\multiprocessing\connection.py", line 149, in Client answer_challenge(c, authkey) File "c:\python27\lib\multiprocessing\connection.py", line 383, in answer_challenge message = connection.recv_bytes(256) # reject large message IOError: [Errno 10035] this is not reasonable, because this behaviour will make subprocess unable to use socket's timeout features globally. Another question is line 138 in managers.py: # do authentication later self.listener = Listener(address=address, backlog=5) self.address = self.listener.address backlog=5 will accept only 5 cocurrent connections, this is stupid, you'd better make this a argument that can be specified by user
msg116376 - (view)	Author: hume (hume)	Date: 2010-09-14 08:30
the above test is on windows
msg116447 - (view)	Author: Jesse Noller (jnoller) *	Date: 2010-09-15 13:54
Calling it stupid doesn't incentivize me to help you, or fix it.
msg116513 - (view)	Author: hume (hume)	Date: 2010-09-16 06:59
Oh, it's obvious that you've found a stupid bug in my description, if that frustrate you, I'd like to say sorry. So I would restate: "this is not so user friendly, would you be kindly enough to fix it?"
msg116876 - (view)	Author: Jesse Noller (jnoller) *	Date: 2010-09-19 16:33
Duplicate; 9897