The peer closed the connection while you were writing to it. That usually means you sent it something it didn’t understand. Is it perhaps an HTTP server? Or some other protocol that you haven’t implemented in your client code?
The reason we got this error is a bug in Windows Server 2008 R2 / Windows 7. The kernel leaks loopback sockets due to a race condition on machines with more than one core, this patch fixes the issue: http://support.microsoft.com/kb/2577795
Your HTTP client disconnected. This could have a couple of reasons: Responding to the request took too long, the client gave up You responded with something the client did not understand The end-user actually cancelled the request A network error occurred … probably more You can fairly easily emulate the behavior: URL url = new … Read more
You are overloading the TCP/IP stack. Windows (and I think all socket stacks actually) have a limitation on the number of sockets that can be opened in rapid sequence due to how sockets get closed under normal operation. Whenever a socket is closed, it enters the TIME_WAIT state for a certain time (240 seconds IIRC). … Read more
java.net.SocketException socket is closed This exception means that you closed the socket, and then continued to try to use it. os.close(); And you closed it here. Closing either the input or the output stream of a Socket closes the other stream and the Socket.
Adding internet permission is not only a solution. You also have to make sure that you are online whether it is mobile or emulator Make sure you are online whether it is mobile or emulator Make sure you have given internet permission in your app’s android/app/src/main/AndroidManifest.xml <uses-permission android:name=”android.permission.INTERNET”/>
Add -Djava.net.preferIPv4Stack=true to the VM options. Another way to confirm if it is the same issue, in Netbeans, right click on the project > properties > Libraries and choose a JDK 6 Java Platform (install if you do not have it). Clean, build then try again. This will eliminate this issue as the problem Credit … Read more
Ok, the answer was that it’s the server’s fault – it had to close the connection after each request. It might be that Android keeps a pool of connections and use the old one or something like that. Anyway , now it works. EDIT: according to the API of HttpURLConnection, this can be solved on … Read more
The javadoc for SocketException states that it is Thrown to indicate that there is an error in the underlying protocol such as a TCP error In your case it seems that the connection has been closed by the server end of the connection. This could be an issue with the request you are sending or … Read more
No connection could be made because the target machine actively refused it?