Name: dc32491 Date: 10/04/2001
The test case has been attached.

java full version "1.3.1._01"


Problem:
Sometimes Windows socket read() does not return to the client even if data is
received on the socket.

Windows JDK version used:
JDK1.3.1_01
JDK 1.3.1-b24
on Windows 2000

AIX 1.3.0 ca130-20010330 on AIX 4.3

  Description:
I have an AIX server, that accepts new client connections and starts out a new
thread to handle the client. Open 7-8 clients on windows to run the client. After
sometime, say 20 msgs have been received by each of the clients, kill all of them
abruptly (cntl+c) except one. This lone client will stop receiving messages from
the server after sometime.

Analysis:
The problem is seen even when the server is run on windows but not very
consistently reproducible. Same case with Solaris too. Using winDump tool to
monitor the client socket shows that data has arrived from the server on the
socket but the client has not received it, which shows that read() has not
returned yet. Only when the client reads the msg, it will write something to the
server & they will continue to exchange messages. Since the read() does not
return, it appears as though the client is hanging. However, a strange behaviour
noticed here is that when a space bar is hit or enter key pressed on this last
client's window, it immediately starts responding.
(Review ID: 133024)
======================================================================