windows TCP连接

[问题]
System.out: can not listen to:java.net.BindException: Address already in use: connect Notify:
解决: http://blog.chinaunix.net/uid-90129-id-132845.html

 短时间内new socket操作过多

  而socket.close()操作并不能立即释放绑定的端口

  而是把端口设置为TIME_WAIT状态

  过段时间(默认240s)才释放(用netstat -na可以看到)

  最后系统资源耗尽

  (windows上是耗尽了pool of ephemeral ports 这段区间在1024-5000之间)

 Socket FAQ:

  Remember that TCP guarantees all data transmitted will be delivered,
if at all possible. When you close a socket, the server goes into a
TIME_WAIT state, just to be really really sure that all the data has
gone through. When a socket is closed, both sides agree by sending
messages to each other that they will send no more data. This, it
seemed to me was good enough, and after the handshaking is done, the
socket should be closed. The problem is two-fold. First, there is no
way to be sure that the last ack was communicated successfully.
Second, there may be "wandering duplicates" left on the net that must
be dealt with if they are delivered.

Andrew Gierth (andrew@erlenstar.demon.co.uk) helped to explain the
closing sequence in the following usenet posting:

Assume that a connection is in ESTABLISHED state, and the client is
about to do an orderly release. The client's sequence no. is Sc, and
the server's is Ss. Client Server
====== ======
ESTABLISHED ESTABLISHED
(client closes)
ESTABLISHED ESTABLISHED

【popexizhi：

用loadrunner 测试nginx max socket connect 个数时，agent端出现的错误，看了是windows的文件句柄限制，但是没有找到修改设置的位置。？？？改linux 做agent去了

】