JDK-6258215 : Num of backlog in ServerSocket(int, int) should be mentioned more explicitly in API document
- Type: Bug
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 1.4.2_08,6
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-04-20
- Updated: 2017-05-16
- Resolved: 2011-05-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.
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 |
|---|
7 b35Fixed  |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Relates :
|
Description
The number of backlog in ServerSocket(int port, int backlog) Constructor is explained
simply as follows.
" Parameters:
port - the specified port, or 0 to use any free port.
backlog - the maximum length of the queue."
http://java.sun.com/j2se/1.4.2/docs/api/index.html
http://java.sun.com/j2se/1.5.0/docs/api/index.html
However, even if we specify preferable number as the number of backlog ,
actual number depends on underlying Opreationg System.
The documnet should say the below(just example).
"Parameters:
port - the specified port, or 0 to use any free port.
backlog - Request of size of the backlog is just passed to underlying OS.
How the OS performs with the request depends on each OS."
=====================================================================
###@###.### 2005-04-20 06:15:45 GMT
Comments
|