SocketException

How to Fix It

1. Read the specific message: 'Connection reset' means the server closed the connection forcibly. 'Broken pipe' means you wrote to a closed connection. 'Connection refused' means nothing is listening at that address/port.

   Each message points to a different cause. Treat them as separate problems rather than one generic network error.

2. For 'Connection reset' and 'Broken pipe': implement retry logic. Catch SocketException, wait a short time, then reconnect and retry the operation. Most transient network errors resolve themselves.

   Example retry pattern: try up to 3 times with exponential backoff (wait 1 second, then 2, then 4). Log each failure so you can monitor how often retries are needed.

3. Configure socket timeouts to avoid hanging forever on dead connections. Set both connect timeout and read timeout: socket.connect(address, 5000) for 5-second connect timeout, socket.setSoTimeout(30000) for 30-second read timeout.

   Without timeouts, a dead connection can cause your program to hang indefinitely waiting for data that will never come.

4. Use connection pooling when making many connections to the same server. Libraries like Apache HttpClient or OkHttp manage connection reuse, health checking, and automatic reconnection for you.

   Creating a new socket for every request is slow and wasteful. Connection pools reuse existing connections and handle stale connection detection automatically.

5. Always close sockets in a finally block or use try-with-resources. Leaked open sockets consume system resources and can cause 'Too many open files' errors over time.

   Example: try (Socket socket = new Socket(host, port)) { ... } — the socket closes automatically when the block ends, even if an exception occurred.