Question

I’ve written a tcp server in Java. It spawns worker instances (Runnable) and listens for incoming tcp connection. Upon connection from a client, it will take in data from the client and does its own processing.

Of late, I noticed that upon client disconnection, the entire server will crash with error java.net.SocketException: Connection reset when the client disconnects or quits. This was when I realised I hadn’t tested the tcp server thoroughly for all instances of failure.

I looked into the code and noticed that the tcp server will crash at this line while((bytesRead…. -1) in the worker instance

final int BUFFSIZE = 65535;
int bytesRead;
byte[] buffer = new byte[BUFFSIZE];
din = new BufferedInputStream(clientSocket.getInputStream());

while ((bytesRead = din.read(buffer)) != -1) {   //tcp server crashes at this line if client quits or disconnects.
// worker does its job.
}

I’ve been pondering about the best way to close worker instance without causing a crash on the tcp server. I don’t have access to the client source code to modify anything on their end.

Any thoughts?

Bregs
Yakult121

Answer 1

Network I/O should be done within a try/catch block if you want to handle exceptions.