blocking read method

[ravinder pasula]

hi all,

I have a typical networking problem, where a clientSocket sends data to a serverSocket. While the client is transmitting a file, and in the middle of it, if client's network fails then at the server end the stream's read method seems to go in infinite loop.
Most craziest part is even after a long time it doesn't seem to throw an exception.
Can anyone help me???

(even though this is a typical networking problem, i somehow feel that there is some problem with the streams, so have put it in streams section)

thanks,
~rkay

[Joe Ess]

Rkay, we try to keep things friendly around here so we ask that everyone use a first name and last name as their displayed name, and that the displayed name is not obviously fake (our naming policy). You can change your displayed name here.
As for your problem. Yes, that sounds unusual. However, I don't think you've given us enough information. How about a small snippet of code?

[ravinder pasula]

Sorry Joe, for hiding my name with rkay.
Here is the code snippet where read method gets blocked.
Here all the out stream part has been removed for simplicity.
Here MAX_BUFFER_SIZE is 8196;
InputStream strm, long dataSize are the inputs to this method:

logger.entering();
spooledFileSize = 0;
try {
byte[] buffer = new byte[MAX_BUFFER_SIZE];
int bytesRead = 0;
int bufsize = 0;
while (true) {
if((dataSize < 0) || ((dataSize-spooledFileSize)>MAX_BUFFER_SIZE)) {
bufsize = MAX_BUFFER_SIZE;
} else {
bufsize = (int) (dataSize-spooledFileSize);
}
bytesRead = strm.read(buffer, 0, bufsize);
if (bytesRead < 0) {
break;
}
spooledFileSize += bytesRead;
if ((dataSize >= 0) && (spooledFileSize>=dataSize)) {
break;
}
}
} catch (SpoolException se) {
logger.exception("caught exception - " + se.getMessage());
} catch (IOException ie) {
logger.error("exception in writing data.");
logger.exception("caught exception - " + ie.getMessage());
} catch(Exception e){
logger.exception("caught exception - " + e.getMessage());
}

thanks
~ravinder

[added [code] tags - Jim]
[ March 19, 2006: Message edited by: Jim Yingst ]