JDK-4969784 : incomplete spec for java.net.Socket.Socket(String,int)
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_2.6
  • CPU: sparc
  • Submitted: 2003-12-17
  • Updated: 2017-05-16
  • Resolved: 2008-10-01
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 7 Other
7 b03Fixed OpenJDK6Fixed
Related Reports
Relates :  
JDK-6285145 - (spec) Unspecified Socket/ServerSocket constructors behavior
Description
Name: ktR10099			Date: 12/17/2003



Specification for java.net.Socket(String host, int port)
does not describe behavior in case port is negative or too large. Current
java implemetation throws IllegalArgumentException, which seems
reasonable.

======================================================================
Comments
EVALUATION This was originally filed against SSLSocket, but it's more appropriate for java.net, since we're consumers of the Socket API. If it's needed, we could put this clarification in both places, but should definately start with Socket. ###@###.### 2003-12-17 Yes it should be documented in the javadoc for the socket API. ###@###.### 2003-12-18 Socket can borrow such documents from InetSocketAddress; InetSocketAddress has documented it. Last but not least, Socket actually delegates the creation of socket address to InetSocketAddress. So it's also good to keep their document in synchronization. ###@###.### 2005-03-16 03:55:22 GMT
16-03-2005