使用EventMachine时为什么会有这么多“TIME_WAIT”连接？
当我运行EventMachine的测试代码时，我发现有太多“ TIME_WAIT ”连接。 这是个问题吗？
运行netstat -anp | grep 8080
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 13012 / ruby
tcp 0 0 127.0.0.1:38701 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38706 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38709 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38708 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38699 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38700 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38707 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38705 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38702 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38703 127.0.0.1:8080 TIME_WAIT -
tcp 0 0 127.0.0.1:38704 127.0.0.1:8080 TIME_WAIT -
我的测试客户端代码是：
require 'rubygems' require 'benchmark' require 'socket' require 'logger' Benchmark.bm do |x| logger = Logger.new('test.log', 10, 1024000) logger.datetime_format = "%Y-%m-%d %H:%M:%S" logger.info "----------------------------------" x.report("times:") do for i in 0..20 sleep 0.1 Thread.new do TCPSocket.open "127.0.0.1", 8080 do |s| s.send "#{i}", 0 if result = s.recv(100) logger.info result end end end end end end
我的测试服务器代码是：
require 'rubygems' require 'benchmark' require 'eventmachine' class Handler ex LOGGER.error "#{ex.class}: #{ex.message}\n#{ex.backtrace.join("\n")}" end def do_something #simulate a long running request a = [] for i in 1..3000 a << rand(3000) a.sort! end return @reply end def callback(msg) self.send_data msg @state = :closing end def unbind close_connection_after_writing #unless @state == :processing end end EventMachine::run { EventMachine.epoll EventMachine::start_server("0.0.0.0", 8080, Handler) puts "Listening..." }
TIME_WAIT状态持续两分钟，并在TCP中提供至关重要的连接安全性。 这不是问题，而是解决方案。