-
Bug
-
Resolution: Fixed
-
P3
-
11, 15, 16, 17
-
b28
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8268987 | 18 | Patrick Concannon | P3 | Resolved | Fixed | b03 |
| JDK-8270570 | 17.0.1 | Patrick Concannon | P3 | Resolved | Fixed | b03 |
| JDK-8269902 | 11.0.13-oracle | Ravi Reddy | P3 | Resolved | Fixed | b03 |
| JDK-8272430 | 11.0.13 | Aleksey Shipilev | P3 | Resolved | Fixed | b03 |
| JDK-8269903 | 8u321 | Ravi Reddy | P3 | Closed | Not an Issue |
Currently, any test that runs without `/othervm` after this test would find the `DatagramSocketImpl` factory created by this test, and therefore any call made to new `DatagramSocket()` would return/use a `NetMulticastSocket` instead of `DatagramSocketAdaptor`. This could make tests that create `DatagramSocket/MulticastSocket` fail intermittently in unexplainable ways. Adding in /othervm to the @run tag will avoid this problem.
- backported by
-
JDK-8268987 Test `ADatagramSocket.java` missing /othervm from @run tag
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- links to
-
Commit
openjdk/jdk11u-dev/51cd6851
-
Commit
openjdk/jdk17/7d7bdbe1
-
Review
openjdk/jdk11u-dev/226
-
Review
openjdk/jdk17/75
-
Review
openjdk/jdk/4493