Java simple code: java.net.SocketException: Unexpected end of file from server

Question

I wrote some simple code in Java, the method should connect to the website and return the BufferedReader.

private BufferedReader getConnection(String url_a) {         URL url;         try {             System.out.println("getting connection");             url = new URL(url_a);             HttpURLConnection urlConnection = (HttpURLConnection)                       url.openConnection();             urlConnection.addRequestProperty("User-Agent",                     "Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.7.3) Gecko/20040924"                      + "Epiphany/1.4.4 (Ubuntu)");             inStream = new InputStreamReader(urlConnection.getInputStream());             return new BufferedReader(inStream);         } catch (Exception ex) {             Logger.getLogger(Reader.class.getName()).log(Level.SEVERE, null, ex);         }         return null;  } 

When I use it on my PC, it works fine but when I put .jar file on the server I get this error:

java.net.SocketException: Unexpected end of file from server at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:718) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:715) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322) at dataconverter.Reader.getConnection(Reader.java.260) 

Problem is quite strange because the exception isn't thrown each time, sometimes everything is OK and program works fine.

Has anybody got any ideas?

Answer 1

"Unexpected end of file" implies that the remote server accepted and closed the connection without sending a response. It's possible that the remote system is too busy to handle the request, or that there's a network bug that randomly drops connections.

It's also possible there is a bug in the server: something in the request causes an internal error, and the server simply closes the connection instead of sending a HTTP error response like it should. Several people suggest this is caused by missing headers or invalid header values in the request.

With the information available it's impossible to say what's going wrong. If you have access to the servers in question you can use packet sniffing tools to find what exactly is sent and received, and look at logs to of the server process to see if there are any error messages.