JDK-8244933 : DatagramSocket.connect does not specify that it may cause datagrams in the socket receive buffer to be discarded
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 15
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2020-05-13
  • Updated: 2024-10-17
  • Resolved: 2020-06-10
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 JDK 16
15 b27Fixed 16Fixed
Related Reports
CSR :  
JDK-8247181 - DatagramSocket.connect does not specify that it may cause datagrams in the socket receive buffer to be discarded
Relates :  
JDK-8235674 - JEP 373: Reimplement the Legacy DatagramSocket API
Description
Currently, the javadoc for `DatagramSocket.connect` doesn't specify that it may cause datagrams in the socket receive buffer that have not been received (by calling receive) to be discarded. That may happen with the DatagramSocket adaptor returned by `DatagramChannel::connect`, and also with the new implementation proposed by JEP 373.
Comments
Changeset: 2e8356ea Author: Patrick Concannon <pconcannon@openjdk.org> Date: 2020-06-10 11:08:19 +0000 URL: https://git.openjdk.java.net/lanai/commit/2e8356ea
02-07-2020
URL: https://hg.openjdk.java.net/jdk/jdk/rev/fca27f266161 User: pconcannon Date: 2020-06-10 10:08:48 +0000
10-06-2020