-
Enhancement
-
Resolution: Fixed
-
P3
-
13
-
b25
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8226041 | 14 | Chris Hegarty | P3 | Resolved | Fixed | team |
ServerSocket.implAccept can be called with a Socket that has an underlying SocketImpl. The Socket may be connected, closed, it may even be a Socket with a SocketImpl that ServerSocket doesn't know anything about.
Minimally we should put a warning into the implAccept method that it only should be called with a newly created/unbound Socket. The warning can make it clear that calling it with a Socket that has SocketImpl may lead to unspecified behavior, maybe even resource leakage.
Minimally we should put a warning into the implAccept method that it only should be called with a newly created/unbound Socket. The warning can make it clear that calling it with a Socket that has SocketImpl may lead to unspecified behavior, maybe even resource leakage.
- backported by
-
JDK-8226041 ServerSocket.implAccept should include warnings about Socket type/state
-
- Resolved
-
- csr for
-
JDK-8225431 ServerSocket.implAccept should include warnings about Socket type/state
-
- Closed
-
- relates to
-
-
- Resolved
-