JDK-4474677 : cannot reopen ServerSocket after close [#4278322 not really fixed?]
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 1.4.0
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2001-06-26
  • Updated: 2001-06-29
  • Resolved: 2001-06-29
Related Reports
Duplicate :  
JDK-4476378 - SO_REUSEADDR broken on Windows
Description

Name: krC82822			Date: 06/26/2001


java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b65)
Java HotSpot(TM) Client VM (build 1.4.0-beta-b65, mixed mode)


restarting our java web server (that is, exit and then run again)
*sometimes* results in an exception about the port being busy
(JVM_Bind). netstat -a shows that the port is marked "closing".
certainly it does not respond to connection attempts. this seems
to be bug #4278322 rearing its ugly head again, except that the
details are slightly different in that with bug #4278322 the jvm
was not exited and established connections were not closed. here
the jvm exits and all connections are closed. the server socket
just cannot be reopened.
(Review ID: 127373) 
======================================================================
Comments
WORK AROUND Name: krC82822 Date: 06/26/2001 waiting a few minutes solves the problem. but this is unacceptable in a production system. switching back to jdk 1.3.1 also solves the problem. ======================================================================
11-06-2004
EVALUATION Submitter has confirmed that server is running with administration privilege. We have an issue on NT and 2000 whereby we use make an exclusive bind when we are privileged. This prevents us binding when the in TIME_WAIT state. For beta-refresh we are fixing the various SO_REUSEADDR issues so closing as duplicate of 4476378. alan.bateman@ireland 2001-06-29
29-06-2001