java.net.SocketException: Connection reset
The remote side closed the TCP connection abruptly while Java was reading or writing.
Exact message you may see
Connection resetSocketException: Connection reset
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 not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Java
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 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.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026