Hi, I get this problem "java.net.SocketException: Connection reset" We are using socket pooling. Ours is a web application that internally connects to a legacy application through sockets. This happens if we login to a page and keep it like that for 1 day and then retry to opertae something. i.e., the sockets are kep[t idle for a day and are tried to be used. it gives error while reading not while writing. And is this different from "connection reset by peer" if so how much different? If it is connection reset by peer then probably we can use 'setKeepAlive()' but I donot see it as like that, since the socket is not closed and we are able to write but the problem comes at the time of reading. Thanks, Santosh
"connection reset" means the connection times out on your end, "connection reset by peer" means it times out on the other end or is lost due to network conditions (which possibly can also trigger "connection reset", not quite sure there).
Joined: Sep 26, 2000
Thanks for the information. Any idea in what cases this may occur at the client side? and how to handle this...as this is observed to occur very vaguely. If it is because of timing out at the time of reading then we are not using setSoTimeOut() for these sockets. [ September 25, 2003: Message edited by: santu j ]
subject: Connection reset vs. connection reset by peer