JDK-8231719 : Correct contradictions in timeout range descriptions
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 14
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-10-01
  • Updated: 2019-10-26
  • Resolved: 2019-10-18
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 14
14 b20Fixed
Related Reports
CSR :  
JDK-8232166 - Correct contradictions in timeout range descriptions
Relates :  
JDK-8231401 - DatagramSocket.setSoTimeout does not specify IAE when timeout is negative
Description
During the review of CSR JDK-8231401, it was observed that DatagramSocket.setSoTimeout, Socket.setSoTimeout and ServerSocket.setTimeout have a contradiction in their description of the valdi range for a timeout value:

"The timeout must be {@code > 0}. A timeout of zero is interpreted as an infinite timeout."

This should be corrected.
Comments
URL: https://hg.openjdk.java.net/jdk/jdk/rev/04946947ca79 User: dfuchs Date: 2019-10-18 17:02:41 +0000
18-10-2019