-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0
-
b18
-
linux
On linux, after calling DatgramChannel::disconnect, DatagramChannel::getLocalAddress reports a soclet address with a local port set to 0.
This appears to be a known side effect to the native `connect` method: DatagramSocket has a work around to palliate the issue (it checks the local address, and if the port is 0, it calls `NET_bind` again. This appears to work on linux, but not on BSD.
java.lang.AssertionError: local address after disconnect should be /127.0.0.1:48591 found /127.0.0.1:0
This appears to be a known side effect to the native `connect` method: DatagramSocket has a work around to palliate the issue (it checks the local address, and if the port is 0, it calls `NET_bind` again. This appears to work on linux, but not on BSD.
java.lang.AssertionError: local address after disconnect should be /127.0.0.1:48591 found /127.0.0.1:0
- blocks
-
-
- Resolved
-
- csr for
-
JDK-8231880 (dc) DatagramChannel::disconnect changes the port of the local address to 0 (lnx)
-
- Closed
-
- relates to
-
-
- Resolved
-
-
JDK-8231261 (dc) Write a test to check local and remote addresses after calling DatagramChannel::connect and DatagramChannel::disconnect
-
- Resolved
-