This week's giveaway is in the Spring forum.
We're giving away four copies of REST with Spring (video course) and have Eugen Paraschiv on-line!
See this thread for details.
The moose likes Sockets and Internet Protocols and the fly likes Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Java » Sockets and Internet Protocols
Bookmark ""Connection reset" problem NOT "Connection reset by peer"" Watch ""Connection reset" problem NOT "Connection reset by peer"" New topic

"Connection reset" problem NOT "Connection reset by peer"

san jan

Joined: Sep 26, 2000
Posts: 24
I get this problem " 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.
I agree. Here's the link:
subject: "Connection reset" problem NOT "Connection reset by peer"
It's not a secret anymore!