[BUG] Socket assumes connection in Linux

Lex Spoon lex at cc.gatech.edu
Mon Mar 26 15:39:59 UTC 2001


ajh18 at cornell.edu wrote:
> When I do:
> 	Socket initializeNetwork.
> 	s _ Socket new connectTo: (NetNameResolver addressFromString:
> '127.0.0.1') port: 2001.
> It always returns a connected socket even when there is no socket
> listening on 2001.
> (s waitForConnectionUntil: Socket standardDeadline) returns true right
> away.  It is not until I attempt to send data that its status changes
> from connected to otherEndClosedButNotThisEnd and an error is raised.
> 
> I am the only one having Linux socket problems?  Can anyone repeat this
> problem or the problem I posted on March 23 entitled "[BUG]Socket waits
> unnecessarily in linux"?
> 

It's been long known, but no one has ever fixed it.  The kernel only
tells the VM that the connection has completed, and doesn't tell it
whether it completed *successfully*.  Or at least, the current VM isn't
reading the kernel's signals.

There is a connectHandler() function that handles this response.  If you
or anyone can fix it, that would be terrific. 


-Lex





More information about the Squeak-dev mailing list