non blocking tcp connect with epoll

linux tcp epoll
doccarcass picture doccarcass · May 20, 2010 · Viewed 11.1k times · Source

My linux application is performing non-blocking TCP connect syscall and then use epoll_wait to detect three way handshake completion. Sometimes epoll_wait returns with both POLLOUT & POLLERR events set for the same socket descriptor.

I would like to understand what's going on at TCP level. I'm not able to reproduce it on demand. My guess is that between two calls to epoll_wait inside my event loop we had a SYN+ACK/ACK/FIN sequence but again I'm not able to reproduce it.

Answer

caf picture caf · May 21, 2010

It is likely for this to happen if the connect has failed - for example with "connection timed out" (for sockets doing a non-blocking connect, POLLOUT becomes set when the connect operation has finished for both successful and unsuccessful outcomes).

When POLLOUT becomes set for the socket, use getsockopt(sock, SOL_SOCKET, SO_ERROR, ...) to check if the connect succeeded or not (the SO_ERROR socket option is 0 in this case, and otherwise indicates why the connect failed).

Related questions

Async connect and disconnect with epoll (Linux)

I need async connect and disconnect for tcp client using epoll for Linux. There are ext. functions in Windows, such as ConnectEx, DisconnectEx, AcceptEx, etc... In tcp server standard accept function is working, but in tcp client doesn't working connect …

Read More
Freeing up a TCP/IP port?

netstat -tulnap shows me what ports are in use. How to free up a port in Linux?

Read More
How to open port in centOS

I have installed and web application which is running on port 8080 on centOS. I only have command line access (through putty) to that machine. I have tried to access that application from my windows machine from which I am connected …

Read More