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.

classification
Title: errno 107 socket.recv issure
Type: Stage:
Components: None Versions: Python 2.6
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: amaury.forgeotdarc, twistedphrame
Priority: normal Keywords:

Created on 2010-02-08 23:46 by twistedphrame, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg99074 - (view) Author: Jordan Apgar (twistedphrame) Date: 2010-02-08 23:46
I have a simple tcp server and client where the server sits and waits for a message and then processes it, my client sends its first message to the server.  On the server I receive: 
socket.error: [Errno 107] Transport endpoint is not connected
when calling
msg = self.socket.recv(self.buffer)

My client receives the error:
socket.error: [Errno 104] Connection reset by peer
when calling    
msg = self.socket.recv(self.buffer)

I was working on the server and client over the weekend and sending and receiving worked fine, I wanted to debug a few things and I get this when I try to run it (no changes made from what I had on the weekend)
msg99094 - (view) Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * (Python committer) Date: 2010-02-09 08:11
The issue tracker is not to a place to find problems in your code (network programming is difficult, even with python).
Please ask your questions on the comp.lang.python newsgroup, where many people will be ready to help you.
msg99116 - (view) Author: Jordan Apgar (twistedphrame) Date: 2010-02-09 14:08
Sorry I was under the impression this was an issue with the socket module
History
Date User Action Args
2022-04-11 14:56:57adminsetgithub: 52135
2010-02-09 14:08:15twistedphramesetmessages: + msg99116
2010-02-09 08:11:17amaury.forgeotdarcsetstatus: open -> closed

nosy: + amaury.forgeotdarc
messages: + msg99094

resolution: not a bug
2010-02-08 23:46:54twistedphramecreate