Bug ID: JDK-7141822 java/nio/channels/DatagramChannel/ChangingAddress.java failing on OS X

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

JDK 15
15Resolved

java/nio/channels/DatagramChannel/ChangingAddress.java fails with Runtime Exception:
Expected: 0.0.0.0/0.0.0.0, actual: /10.132.188.76
	at ChangingAddress.check(ChangingAddress.java:43)
	at ChangingAddress.main(ChangingAddress.java:61)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:722)

Reclosing as a duplicate of JDK-8241072 .
18-05-2020
Only bugs associated with changesets should be closed as "Fixed".
18-05-2020
Fixed as part of JDK-8241072
18-05-2020
We should remove that test from the ProblemList.txt in the JDK-8230211-branch
15-04-2020
I confirm that the test passes with the new implementation in the JDK-8230211-branch of the sandbox that contains the prototype information for the JEP JDK-8235674 Reimplement the Legacy DatagramSocket API. The legacy implementation still has the issue.
12-02-2020
If JDK-8230211 goes ahead, the test could be re-enabled, since it asserts consistent behavior between the channel's adapter and datagram socket. But, in fact datagram channel and the datagram channel's adapter are actually returning an unexpected address, not datagram socket, see JDK-8231259.
17-10-2019
If JDK-8230211 (or a sub-task/related issue) drops the emulation of connected datagrams from DatagramSocket then I assume this test can be re-enabled.
26-09-2019
Mentioned test in ProblemList.txt, re-tested and still fail on macOS with JDK 11.
13-06-2018
Likely a configuration issue.
31-10-2017
Dan - I think you need to check the configuration for these test runs as this test is excluded on OS X (see jdk/test/ProblemList.txt)
27-09-2014
EVALUATION This is occuring because of the recent push for 7122794, the native function corresponding to datagramsocket.connect() is never getting called on mac os x.
02-02-2012

Duplicate :	JDK-7084030 - DatagramSocket.getLocalAddress inconsistent on XP/2003 when IPv6 enabled and socket is connected
Duplicate :	JDK-8231259 - (dc) DatagramChannel::disconnect re-binds socket to the wildcard address (macOS)
Relates :	JDK-8230211 - Prepare DatagramSocket for alternative DatagramSocketImpl
Relates :	JDK-8241072 - Reimplement the Legacy DatagramSocket API
Relates :	JDK-8231259 - (dc) DatagramChannel::disconnect re-binds socket to the wildcard address (macOS)