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 giampaolo.rodola
Recipients Arfrever, flox, giampaolo.rodola, janssen, pitrou, vstinner
Date 2010-03-25.19:33:18
SpamBayes Score 9.4788156e-08
Marked as misclassified No
Message-id <1269545601.31.0.0602952173445.issue8108@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, I've finally been able to reproduce the issue by installing OpenSSL 0.9.8m on my Ubuntu box.
By doing some debugging I'm starting to think that maybe there's something wrong with the shutdown() method implementation itself because no matter what, sooner or later it always ends up raising "error: [Errno 0] Error".

I've cheated by trapping shutdown() in a while loop waiting for it to succeed, I've tried to manually call handle_read() and handle_write(), I've also tried to set the socket back to blocking mode just to see if shutdown() would return but I've always ended up encountering "error: [Errno 0] Error".

IMHO, before going any further I'd investigate on why this call can just fail without providing any information about what happened.
From the upper application's point of view there's nothing it can do in case of such an error.
Assuming that "the remote side closed the connection abruptly" and close the socket is just wrong.
History
Date User Action Args
2010-03-25 19:33:21giampaolo.rodolasetrecipients: + giampaolo.rodola, janssen, pitrou, vstinner, Arfrever, flox
2010-03-25 19:33:21giampaolo.rodolasetmessageid: <1269545601.31.0.0602952173445.issue8108@psf.upfronthosting.co.za>
2010-03-25 19:33:19giampaolo.rodolalinkissue8108 messages
2010-03-25 19:33:18giampaolo.rodolacreate