[Twisted-Python] self.socket.accept() in doRead() in tcp.py has (11, 'Resource temporarily unavailable') error
Hello everyone, I have been trying to debug a Twisted app of mine and I noticed that in tcp.py in doRead() self.socket.accept() raises the following exception : error: (11, 'Resource temporarily unavailable'). It seems to just smother the exception though. I read in the python doc that sockets raise that exception if the call would block, when the socket is configuered in non-blocking mode. It seems to do that because the data it receives is too big, how am I supposed to resolve this? Thank you, Gabriel
On 11:43 am, gabriel.rossetti@arimaz.com wrote:
Hello everyone,
I have been trying to debug a Twisted app of mine and I noticed that in tcp.py in doRead() self.socket.accept() raises the following exception : error: (11, 'Resource temporarily unavailable'). It seems to just smother the exception though. I read in the python doc that sockets raise that exception if the call would block, when the socket is configuered in non-blocking mode. It seems to do that because the data it receives is too big, how am I supposed to resolve this?
This exception is normal, correct, and harmless. Whatever in your app is not behaving as you would like, it is almost certainly not related to this exception. socket.accept() how new connections are accepted. This is not related to how data is read from connections. Jean-Paul
exarkun@twistedmatrix.com wrote:
On 11:43 am, gabriel.rossetti@arimaz.com wrote:
Hello everyone,
I have been trying to debug a Twisted app of mine and I noticed that in tcp.py in doRead() self.socket.accept() raises the following exception : error: (11, 'Resource temporarily unavailable'). It seems to just smother the exception though. I read in the python doc that sockets raise that exception if the call would block, when the socket is configuered in non-blocking mode. It seems to do that because the data it receives is too big, how am I supposed to resolve this?
This exception is normal, correct, and harmless. Whatever in your app is not behaving as you would like, it is almost certainly not related to this exception.
socket.accept() how new connections are accepted. This is not related to how data is read from connections.
Jean-Paul
Ok, thank you Jean-Paul. My app just drops those msgs, if I make them smaller they go though, so I though maybe that was it. Gabriel
participants (2)
-
exarkun＠twistedmatrix.com -
Gabriel Rossetti