This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients benjamin.peterson, donmez, jnoller, mark.dickinson
Date 2008-08-02.13:44:18
SpamBayes Score 7.39088e-05
Marked as misclassified No
Message-id <>
> Are you looking at the conn refused or the incref error?

The connection refused error.

The attached patch fixes the problem, for me.  On my machine, the 
connection refused error code was 61 rather than 10061.  With this patch, 
I'm no longer seeing any hangs in (at least, not in 
the last 500 runs :-)).  (Though I am still seeing the incref error 

If anyone's prepared to answer a stupid question:  I'm curious why failed 
socket connections occur at all.  Is connecting to a socket generally 
considered an unreliable operation, or is there some aspect of the 
multiprocessing module that makes it potentially unreliable?
Date User Action Args
2008-08-02 13:44:21mark.dickinsonsetrecipients: + mark.dickinson, donmez, benjamin.peterson, jnoller
2008-08-02 13:44:20mark.dickinsonsetmessageid: <>
2008-08-02 13:44:19mark.dickinsonlinkissue3419 messages
2008-08-02 13:44:19mark.dickinsoncreate