Why am I getting a SocketException in a long running application?

Question

I have written a Java socket server application which is giving me error if i run it for long time say 4-8hrs, below is the list of error i get:

java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:130)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:282)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:324)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:176)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.fill(BufferedReader.java:153)
        at java.io.BufferedReader.readLine(BufferedReader.java:316)
        at java.io.BufferedReader.readLine(BufferedReader.java:379)
        at LiveRate.processData(LiveRate.java:224)
        at LiveRate.mainLiveRate(LiveRate.java:265)
        at LiveRate.liveRate(LiveRate.java:126)
        at LiveRate.run(LiveRate.java:119)
        at java.lang.Thread.run(Thread.java:636)

My socket application reads some values from another TCP/IP server and stores the value temporarily and offers the same to other client.Not sure If these error are because of Heavyload on the system or because of the Memory issues.Please help

This question may give you some pointers: http://stackoverflow.com/questions/585599/whats-causing-my-java-net-socketexception-connection-reset — Richard H, May 16 '11 at 11:55

score 4 · Answer 1 · answered May 16 '11 at 12:04

It is probably neither (directly) load or memory related. Instead, it is more likely to be one of the following:

the remote service is shut down / falls over and is restarted on a regular basis,
the remote service has decided to close its end of the connection because it is "idle",
network connectivity is intermittent and you are occasionally encountering an outage or congestion-induced "brownout" that is too long,
you are using NAT or similar, and the port number that was being used for the connection has been reclaimed by the NAT gateway, or
something is enforcing some policy about TCP/IP connections being open for too long.

The bottom line is that your client software needs to be able to cope with lost connections if you want ti to run for extended periods of time. This is the way that the internet works.

score 0 · Answer 2 · answered May 16 '11 at 11:55

0

I'd say it's because your connection gets reseted by your Internet Provider every 24 hours.

answered May 16 '11 at 11:55

Lukas Knuth

25,449
15
83
111

1

Bit of a shot in the dark considering the OP says they only need to run it for 4 to 8 hours... – forsvarir May 16 '11 at 11:56
When the connection gets reset within this 4 to 8 hours, that's where the problem lays. – Lukas Knuth May 16 '11 at 11:59
Bit of a shot in the dark considering you don't know who the ISP is or what their policies are. – user207421 May 17 '11 at 02:00

Why am I getting a SocketException in a long running application?

2 Answers2