United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-6483406 : new ServerSocket() sometimes takes more than 3 minutes on Suse Linux

Details
Type:
Bug
Submit Date:
2006-10-18
Status:
Closed
Updated Date:
2011-05-18
Project Name:
JDK
Resolved Date:
2011-05-18
Component:
core-libs
OS:
generic
Sub-Component:
java.net
CPU:
generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:

Related Reports

Sub Tasks

Description
Sometimes on Suse Linux machines, call to ServerSocket default constructor can take more than 3 minutes.

Here is the stack trace:
        at java.net.PlainSocketImpl.initProto(Native Method)
        at java.net.PlainSocketImpl.<clinit>(PlainSocketImpl.java:84)
        at java.net.ServerSocket.setImpl(ServerSocket.java:236)
        at java.net.ServerSocket.<init>(ServerSocket.java:61)
        at ServerSocketCreateTest.main(ServerSocketCreateTest.java:9)

Attached program and script can be used to reproduce this.

It seems that it is waiting for some timeout.

                                    

Comments
EVALUATION

I've raised the priority as the problem seems to be more widespread than initially thought. Will also consider a backport to JDK 6.
                                     
2008-05-08
EVALUATION

The only thing that can block for such a long time in initProto() is the creation of the markerFD. Switching to socketpair() calls, as we are planning to do, should solve this.
                                     
2006-10-27



Hardware and Software, Engineered to Work Together