-
Bug
-
Resolution: Fixed
-
P3
-
17
-
b27
-
Verified
The new SocketImpl introduced under JEP 353 does not close the underlying socket when the connect method rejects an unresolved address. The old SocketImpl used to close the socket in this case, leaving the Socket open, but at least the underlying socket is released. We expect the implementation to do the same. Unlike SocketChannel.connect, Socket.connect does not document the behaviour when connect fails.
- csr for
-
JDK-8344527 Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs
-
- Closed
-
- relates to
-
JDK-8345176 Add tests to verify java.net.Socket constructors close the socket on failure
-
- Resolved
-
-
JDK-8346017 Socket.connect specified to throw UHE for unresolved address is problematic for SOCKS V5 proxy
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/3eb54615
-
Review(master) openjdk/jdk/22160
There are no Sub-Tasks for this issue.