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 orsenthil
Recipients ajaksu2, orsenthil, python-dev, reowen, sschwarzer
Date 2011-07-03.20:05:49
SpamBayes Score 0.0026028967
Marked as misclassified No
Message-id <20110703200545.GB3937@mathmagic>
In-reply-to <1309164343.54.0.647232997116.issue1067702@psf.upfronthosting.co.za>
Content
Hello Stefen, 

Yes, I was able to reproduce the issue without the patch and at the
same time, noticed that the problem was not observed in other branches
(py3k), then saw the differences where the possible socket close
delays can happen and fixed it. As it was multiple threads closely
being closed it was most probably due to delay in closing socket
connection that lead the problem in the first place.

If it is required, then manually this can be verified by setting up an
artificial delay in the network layer and trying multiple ftp
transfers. (No, I did not do that to verify. :))
History
Date User Action Args
2011-07-03 20:05:50orsenthilsetrecipients: + orsenthil, reowen, sschwarzer, ajaksu2, python-dev
2011-07-03 20:05:49orsenthillinkissue1067702 messages
2011-07-03 20:05:49orsenthilcreate