This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: select() hangs sometimes, for TCP connections
On Fri, Feb 13, 2004 at 08:28:36PM +0100, Corinna Vinschen wrote:
>On Feb 13 09:32, Christopher Faylor wrote:
>>On Fri, Feb 13, 2004 at 04:27:19AM -0800, Patrick Samson wrote:
>>>Problem: sometimes select() doesn't return.
>>>
>>>Context: I run a DB replication scenario, with cron, everything 5 mn.
>>>There is no change in the DB, so the scenario is always the same. Most
>>>of the time, it works. But eventually, after some time (may be some
>>>minutes or hours), a process A keeps waiting forever in select() for a
>>>response on a TCP socket. With gdb I can see that the other end B
>>>returned in its ReadCommand() function, meaning it has send its
>>>response and waits for a new command, so this side should be OK.
>>
>>I suspect that this is basically a winsock socket reuse bug that has
>>been around for a long time.
>>
>>Corinna, does this ring a bell?
>
>Hmm... no, not off top of my head. Any additional hint?
Wasn't there a problem where a port was reused that wasn't exactly ready
to be reused or something? I'm sorry that I don't remember exactly.
It just feels vaguely like a problem we threw our hands up on a while
ago.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/