"bad file descriptor" from tcp sockets 
Author Message
 "bad file descriptor" from tcp sockets

ok, im binding a listening socket with TCPServer, looping for inbound
connections, passing the accepted sockets off to another part of the program.
Now this doesn't happen often, and ive yet to provoke it intentionally, but
after the server is running for a while, all of the sudden the gets loop for
each of the accepted sockets in the application raise an exception with the
message Bad File Descriptor, and the listening socket isnt listening anymore.
Any ideas on whats happening here? It would make sense to me if it was raised
on only the sockets accepted after a certain point in execution, but its raised
on all of them, an hour after the server has been started and in the midst of
the accepted sockets communicating fine.

Sat, 09 Jul 2005 21:15:42 GMT  
 [ 1 post ] 

 Relevant Pages 

1. socket.error: (9, 'Bad file descriptor')

2. Socket Help "Socket Newbie"

3. DPMI "Set descriptor" call

4. T edit descriptor and ADVANCE="NO"

5. Fortran "logical unit" to C "stream/file descriptor" (fwd)

6. Fortran "logical unit" to C "stream/file descriptor"

7. string.join(["Tk 4.2p2", "Python 1.4", "Win32", "free"], "for")

8. Printing "bad" font

9. "ep": Bad News

10. "Bad Managers" website

11. OS/2 "standard" TCP/IP

12. "bad synchronous description" in Xilinx WebPack


Powered by phpBB® Forum Software