Comment 6 for bug 411349

I now have a server process that seems to idle, and /proc/[pid]/task/ only contains a single pid (the main thread). The log states:
[24839] 2009-08-11 13:59:05.109 WARNING: listening socket error: (11, 'Resource temporarily unavailable')
[24839] 2009-08-11 13:59:30.820 WARNING: listening socket error: (11, 'Resource temporarily unavailable')

In the meantime the client stays blocked on a recvfrom(4,...)

I logged open connections and found something very odd: the client is waiting on a connection it thinks is open:
bzr 21626 jal 4u IPv4 1165611 TCP 172.22.128.28:44635->192.168.0.110:4155 (ESTABLISHED)

The server has no task running, and actually does not have this connection anymore:
[root@mouse ~]# netstat -n | grep \.28\:
tcp 0 0 192.168.0.110:1521 172.22.126.28:1702 ESTABLISHED
tcp 0 0 192.168.0.110:1521 172.22.126.28:2176 ESTABLISHED
tcp 0 0 192.168.0.110:1521 172.22.126.28:1516 ESTABLISHED
tcp 0 0 192.168.0.110:1521 172.22.126.28:2174 ESTABLISHED
tcp 0 0 192.168.0.110:1521 172.22.126.28:2171 ESTABLISHED
tcp 0 0 192.168.0.110:1521 172.22.126.28:1127 ESTABLISHED
tcp 0 0 192.168.0.110:445 172.22.126.28:1094 ESTABLISHED
tcp 0 0 192.168.0.110:445 172.22.126.28:1098 ESTABLISHED
tcp 0 512 ::ffff:192.168.0.110:22 ::ffff:172.22.128.28:34085 ESTABLISHED

Either the connection has been idle for so long that the firewall caused a close or!?