-
Bug
-
Resolution: Fixed
-
P2
-
8, 11, 14, 15
-
b14
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8242005 | 14.0.2 | Andrew Brygin | P2 | Resolved | Fixed | b04 |
| JDK-8246313 | 13.0.4 | Andrew Brygin | P2 | Resolved | Fixed | b04 |
| JDK-8241509 | 11.0.8-oracle | Andrew Brygin | P2 | Closed | Fixed | b01 |
| JDK-8241872 | 11.0.8 | Andrew Brygin | P2 | Resolved | Fixed | b01 |
| JDK-8261783 | openjdk8u | David Alvarez | P2 | New | Unresolved | |
| JDK-8243685 | 8u261 | Prasadarao Koppula | P2 | Closed | Fixed | b05 |
| JDK-8247018 | emb-8u261 | Prasadarao Koppula | P2 | Resolved | Fixed | team |
The problem seems to be SSLSocket in JDK11 when it receives a SocketTImeoutException will close both the endpoints and the socket, thereby disallowing retries by the peer.
However, in JDK8 we have noticed that in such cases, the end-point is not closed, and allows further retries from the client.
This seems to be an incompatible behavior change and is seriously blocking our development efforts.
Reproducer attached
Debug traces are below.
- backported by
-
JDK-8241872 SSLSocket closes socket both socket endpoints on a SocketTimeoutException
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- New
-
- duplicates
-
-
- Closed
-
- relates to
-
-
- Resolved
-