You should be able to track if there's any exception occured to the sockets in question, of course that's assuming that you're performing IO on them, such as attempting to read or write on the sockets. One thing you should keep watch for is the variable that keeps track of the socket is being overriden, since Java Garbage Collection kicks in when the reference to an object reaches 0, as result the socket gets closed. If that happens, your client should also tell if the connection is gone. On the other hand, the connection is still there; you just don't have a thread to poll on the socket. Good luck. -- Yuwinf Greg Walker <[EMAIL PROTECTED]> wrote: I am having a problem with a server written in java that uses sockets. The server runs fine; the problem arises when I try to access it. The client is simply telnet and after making a connection, and receiving a handful of bytes, the client hangs as if the server is not responding. Yet the server seems to be fine because I can establish another connection to it. This problem goes away if I use the java -debug option (which incidentally throws an exception) or run the server with jdb. I am using jdk1.1.7b and RedHat 6.0 (kernel 2.2.5-15). There was a rumor that java 1.1.6 had a bug with sockets which was fixed in 1.1.7, but I can't locate the docs and I still seem to have a problem. On additional note, ... the server ran fine while I was using a dynamic DHCP address. Once my provider switched me to a static IP address, this problem appeared. Any ideas ? Thanks, -- Greg Walker [EMAIL PROTECTED] ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com. ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
