Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Fri, 13 Feb 2004 09:32:40 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: select() hangs sometimes, for TCP connections
Message-ID:	<20040213143240.GC4672@redhat.com>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20040213122720 DOT 17765 DOT qmail AT web60301 DOT mail DOT yahoo DOT com>
Mime-Version:	1.0
In-Reply-To:	<20040213122720.17765.qmail@web60301.mail.yahoo.com>
User-Agent:	Mutt/1.4.1i
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

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?

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/

- Raw text -