-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b14
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8272770 | 11.0.14-oracle | Evan Whelan | P4 | Resolved | Fixed | b01 |
JDK-8274125 | 11.0.14 | Christoph Langer | P4 | Resolved | Fixed | b01 |
java.net.Socket has existing behavior that is not well exercised by the existing tests. Specifically this issue adds tests for
- invoking shutdownInput/shutdownOutput when a thread is blocked in read/write
- create a deprecated constructor that creates a UDP socket
- connection reset, to test the behavior specified by Socket::getInputStream
- timeout handling. The existing tests for timed connect, read and accept don't exercise many scenarios
- invoking shutdownInput/shutdownOutput when a thread is blocked in read/write
- create a deprecated constructor that creates a UDP socket
- connection reset, to test the behavior specified by Socket::getInputStream
- timeout handling. The existing tests for timed connect, read and accept don't exercise many scenarios
- backported by
-
JDK-8272770 New tests for java.net.Socket to exercise long standing behavior
-
- Resolved
-
-
JDK-8274125 New tests for java.net.Socket to exercise long standing behavior
-
- Resolved
-
- relates to
-
JDK-8221481 Reimplement the Legacy Socket API
-
- Resolved
-