I have an app that acts as a server, and a java program, that connects to it via a TCP socket. The app then waits for commands from the client by calling DataInputStream.readInt(). If I then shut down the client application (when the socket connection is established, and the server is blocking at readInt()), a EOFException is thrown. If I catch it with a IOException Handler though, the Exception object is null! If I catch it with a EOFException Handler, it is a normal EOFException...
It works well, when I just use the EOFException Handler, I'm just curious, is this a bug, or a logical behaviour? I didn't know that Exception objects can be null... In a Stackoverflow question (http://stackoverflow.com/questions/3949609/exception-is-null-always) somebody had a similar problem, and one answer was that "Eclipse probably can't get a correct instance of this exception", but I do not understand what that means, could somebody explain?
Fire me boy! Cool, soothing, shameless self promotion:
the new thread boost feature: great for the advertiser and smooth for the coderanch user