java.net.SocketException: Connection reset
The remote side closed the TCP connection abruptly while Java was reading or writing.
Seen on:
Java
Meaning
Server crashes, load balancer idle timeouts, TLS version mismatches, or reusing a stale pooled connection.
Common causes
- Stale keep-alive connection reused
- Server or proxy closing idle connections
- TLS protocol mismatch
- Request too large for the server
⚡ Quick fix
- Retry idempotent requests once
- Evict idle connections in the HTTP client pool
- Check server logs at that timestamp
Detailed fix by platform
Java
- Apache HttpClient:
evictIdleConnections(TimeValue.ofSeconds(30))
How to diagnose
- When — First request or reused connection?
- Server — Crash/timeout at that time?
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026