Message138765
| Author |
vstinner |
| Recipients |
neologix, pitrou, vstinner |
| Date |
2011年06月20日.23:27:39 |
| SpamBayes Score |
1.716207e-05 |
| Marked as misclassified |
No |
| Message-id |
<1308612460.24.0.921861375514.issue12364@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Message on a stackoverflow thread:
"I have suffered from the same problem, even if connecting on localhost in python 2.7.1. After a day of debugging i found the cause and a workaround:
Cause: BaseProxy class has thread local storage which caches the connection, which is reused for future connections causing "broken pipe" errors even on creating a new Manager
Workaround: Delete the cached connection before reconnecting
if address in BaseProxy._address_to_local:
del BaseProxy._address_to_local[self.address][0].connection"
http://stackoverflow.com/questions/3649458/broken-pipe-when-using-python-multiprocessing-managers-basemanager-syncmanager/5884967#5884967
---
See also maybe the (closed) issue #11663: multiprocessing doesn't detect killed processes |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年06月20日 23:27:40 | vstinner | set | recipients:
+ vstinner, pitrou, neologix |
| 2011年06月20日 23:27:40 | vstinner | set | messageid: <1308612460.24.0.921861375514.issue12364@psf.upfronthosting.co.za> |
| 2011年06月20日 23:27:39 | vstinner | link | issue12364 messages |
| 2011年06月20日 23:27:39 | vstinner | create |
|