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 jnoller
Recipients benjamin.peterson, donmez, jnoller, mark.dickinson
Date 2008-08-02.14:23:56
SpamBayes Score 7.5565e-07
Marked as misclassified No
Message-id <>
In-reply-to <>
On Aug 2, 2008, at 9:44 AM, Mark Dickinson <>  

> Mark Dickinson <> added the comment:
>> 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
> occasionally.)
> 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?

I believe the conn refused error is another race, the child processes  
are connecting to a manager which is shutting down/gone

Thanks again mark- when I get a chance today I'll review/test/apply  
the patch
Date User Action Args
2008-08-02 14:23:57jnollersetrecipients: + jnoller, mark.dickinson, donmez, benjamin.peterson
2008-08-02 14:23:56jnollerlinkissue3419 messages
2008-08-02 14:23:56jnollercreate