[4834] in java-interest
Beta2 changes socket.close() behaviour ?
daemon@ATHENA.MIT.EDU (Bob Beck)
Tue Jan 16 16:25:42 1996
From: rbk@ibeam.jf.intel.com (Bob Beck)
To: java-interest@java.sun.com
Date: Tue, 16 Jan 1996 10:53:09 -0800 (PST)
I have some simple client/server applications written in Java. I was working
on a new one and noticed that when the server closes its socket, the client
doesn't notice this! In Beta1, the client did notice (re-compiling code
that's identical except for beta2 required changes that don't effect this
issue, I think).
For example, a simple server that just echoes its input back to the client
(until the client types "quit"), exercised with telnet: on Beta1 when the
client types "quit", the server closes its socket and telnet reports the
connection to the server went away. Compiled on beta2, it *doesn't* go
away... telnet think's it still attached, but the server thinks its closed
the socket (I've verified I *am* calling socket.close(), and the call
succeeds - no exception).
Has anyone else seen this? It makes it kind of hard to know when the socket
will actually be closed... How else can the server ensure its connection to
the client is really gone (so the client doesn't hang) ??
Any/all help greatly appreciated.
BTW: This is all on Windows NT.
--
Bob Beck rbk@ibeam.intel.com rbk@teleport.com
Intel Corporation (503)264-8856 AOL: RDBeck CIS: 71674,106
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
