Python Tornado Websocket 连接在关闭后仍然打开
Python Tornado Websocket Connections still open after being closed
我有一个 Tornado Websocket 服务器,我想在 30 分钟不活动后超时。我使用 self.close()
在 30 分钟不活动后关闭连接。但似乎有些连接在关闭后仍保持打开状态。
这里是代码的主要部分(从这里得到帮助后实现:):
打开连接:
class WebSocketHandler(tornado.websocket.WebSocketHandler):
def open(self, *args):
self.id = self.generate_id()
self.stream.set_nodelay(True)
# ... DO STUFF ...
self.ini_time = datetime.now()
self.message_number = 0
self.last_message_time = self.ini_time
self.write_message("Connection SUCCESSFUL! Thanks for connecting! Your connection ID is: %d :)" % self.id)
self.timeout = tornado.ioloop.IOLoop.current().add_timeout(timedelta(minutes=30), self.force_close)
print datetime.now()
print "New connection. ID: %d" % self.id
print "Total number of open connections: %d" % len(clients)
收到消息时:
def on_message(self, message):
"""
when we receive some message we want some message handler..
for this example i will just print message to console
"""
if self.timeout:
tornado.ioloop.IOLoop.current().remove_timeout(self.timeout)
self.timeout = tornado.ioloop.IOLoop.current().add_timeout(timedelta(minutes=30), self.force_close)
self.last_message_time = datetime.now()
self.message_number+=1
print datetime.now()
print "Client %s sent message : %s" % (self.id, message)
# ... DO STUFF ...
关闭时:
def on_close(self):
self.common_close()
def common_close(self):
print datetime.now()
print "Open connections are:"
print clients.keys()
print "Closing connection %d." % self.id
end = datetime.now()
timeonline = end - self.ini_time
timeconlastmsg = self.last_message_time - self.ini_time
print "Total time online:"
print timeonline
print "Time between connection start and last message received:"
print timeconlastmsg
if self.id in clients.keys():
del clients[self.id]
print "Number of open connections: %d" % len(clients)
print "Open connections are:"
print clients.keys()
超时:
def force_close(self):
timout = datetime.now()
print timout
print "Connection %d timed out, server is dropping the connection." % self.id
self.common_close()
self.close()
超时生效,函数force_close
被调用。但似乎即使在被调用并从 clients
中删除连接后,连接仍然打开并处于活动状态。
这是程序的示例输出:
New connection. ID: 66919
Total number of open connections: 3
2015-07-14 21:51:48.387892
New connection. ID: 12012
Total number of open connections: 4
2015-07-14 21:51:48.641603
Open connections are:
[66919, 12012, 11281, 97458]
Closing connection 66919.
Total time online:
0:00:00.404316
Time between connection start and last message received:
0:00:00
Number of open connections: 3
Open connections are:
[12012, 11281, 97458]
... ...
Number of open connections: 4
Open connections are:
[66246, 12012, 97458, 6069]
2015-07-14 22:21:47.906129
Connection 97458 timed out, server is dropping the connection.
2015-07-14 22:21:47.906167
Open connections are:
[66246, 12012, 97458, 6069]
Closing connection 97458.
Total time online:
0:30:00.000450
Time between connection start and last message received:
0:00:00
Number of open connections: 3
Open connections are:
[66246, 12012, 6069]
2015-07-14 22:21:48.237407
Connection 66919 timed out, server is dropping the connection.
2015-07-14 22:21:48.237444
Open connections are:
[66246, 12012, 6069]
Closing connection 66919.
Total time online:
0:30:00.000143
Time between connection start and last message received:
0:00:00
Number of open connections: 3
可以看出,66919 是 "closed" 两次,间隔为 30 分钟。有什么想法吗?
另一个连接 3358 被关闭的例子,当假设没有更多打开的连接时(再次关闭两次,间隔 30 分钟):
Open connections are:
[7046, 16287]
2015-07-15 11:01:13.604125
New connection. ID: 3358
Total number of open connections: 3
2015-07-15 11:01:28.429574
Open connections are:
[7046, 3358, 16287]
Closing connection 3358.
Total time online:
0:00:14.825568
Time between connection start and last message received:
0:00:00
Number of open connections: 2
Open connections are:
[7046, 16287]
--
Open connections are:
[]
2015-07-15 11:31:13.629530
Connection 3358 timed out, server is dropping the connection.
2015-07-15 11:31:13.629586
Open connections are:
[]
Closing connection 3358.
Total time online:
0:30:00.025556
Time between connection start and last message received:
0:00:00
Number of open connections: 0
Open connections are:
[]
有人指出我不应该在force_close
中调用common_close
,因为on_close
会被self.close()
调用,但是on_close()
不会' 被 self.close()
调用。
看起来两个重复的 id 正好相隔 30 分钟。这只能说明一件事,当连接被关闭时,另一个定时器被调度,第二个定时器在超时时打印重复的日志。从您的代码判断,这只会发生在 on_message
.
您的客户端如何处理连接关闭?客户端是否有可能在收到 FIN 后立即向服务器发送消息?
在龙卷风源代码中,
# Give the client a few seconds to complete a clean shutdown,
# otherwise just close the connection.
self._waiting = self.stream.io_loop.add_timeout(
self.stream.io_loop.time() + 5, self._abort)
所以服务器给客户端5秒的时间来终止连接,如果客户端在这5秒内向服务器发送消息,可能会出问题。
这只是我的猜测。
common_close
被调用两次,但连接仅超时一次。在您的第一个示例中,66919 在 21:51 处关闭,因为客户端完全关闭了连接(通过 on_close
),然后由于超时再次在 22:21 处关闭。连接对象即使在关闭后仍然存在。连接未打开;只有超时仍然有效。如果 on_close
(或 common_close
)处于活动状态,您需要删除超时。
您还应该在 open()
开始第一次超时而不是等待 on_message()
,并且 force_close()
应该将 self.timeout
设置为 None。
因为 Tornado 4.1 on_close()
将被 self.close()
调用。
我有一个 Tornado Websocket 服务器,我想在 30 分钟不活动后超时。我使用 self.close()
在 30 分钟不活动后关闭连接。但似乎有些连接在关闭后仍保持打开状态。
这里是代码的主要部分(从这里得到帮助后实现:
打开连接:
class WebSocketHandler(tornado.websocket.WebSocketHandler):
def open(self, *args):
self.id = self.generate_id()
self.stream.set_nodelay(True)
# ... DO STUFF ...
self.ini_time = datetime.now()
self.message_number = 0
self.last_message_time = self.ini_time
self.write_message("Connection SUCCESSFUL! Thanks for connecting! Your connection ID is: %d :)" % self.id)
self.timeout = tornado.ioloop.IOLoop.current().add_timeout(timedelta(minutes=30), self.force_close)
print datetime.now()
print "New connection. ID: %d" % self.id
print "Total number of open connections: %d" % len(clients)
收到消息时:
def on_message(self, message):
"""
when we receive some message we want some message handler..
for this example i will just print message to console
"""
if self.timeout:
tornado.ioloop.IOLoop.current().remove_timeout(self.timeout)
self.timeout = tornado.ioloop.IOLoop.current().add_timeout(timedelta(minutes=30), self.force_close)
self.last_message_time = datetime.now()
self.message_number+=1
print datetime.now()
print "Client %s sent message : %s" % (self.id, message)
# ... DO STUFF ...
关闭时:
def on_close(self):
self.common_close()
def common_close(self):
print datetime.now()
print "Open connections are:"
print clients.keys()
print "Closing connection %d." % self.id
end = datetime.now()
timeonline = end - self.ini_time
timeconlastmsg = self.last_message_time - self.ini_time
print "Total time online:"
print timeonline
print "Time between connection start and last message received:"
print timeconlastmsg
if self.id in clients.keys():
del clients[self.id]
print "Number of open connections: %d" % len(clients)
print "Open connections are:"
print clients.keys()
超时:
def force_close(self):
timout = datetime.now()
print timout
print "Connection %d timed out, server is dropping the connection." % self.id
self.common_close()
self.close()
超时生效,函数force_close
被调用。但似乎即使在被调用并从 clients
中删除连接后,连接仍然打开并处于活动状态。
这是程序的示例输出:
New connection. ID: 66919
Total number of open connections: 3
2015-07-14 21:51:48.387892
New connection. ID: 12012
Total number of open connections: 4
2015-07-14 21:51:48.641603
Open connections are:
[66919, 12012, 11281, 97458]
Closing connection 66919.
Total time online:
0:00:00.404316
Time between connection start and last message received:
0:00:00
Number of open connections: 3
Open connections are:
[12012, 11281, 97458]
... ...
Number of open connections: 4
Open connections are:
[66246, 12012, 97458, 6069]
2015-07-14 22:21:47.906129
Connection 97458 timed out, server is dropping the connection.
2015-07-14 22:21:47.906167
Open connections are:
[66246, 12012, 97458, 6069]
Closing connection 97458.
Total time online:
0:30:00.000450
Time between connection start and last message received:
0:00:00
Number of open connections: 3
Open connections are:
[66246, 12012, 6069]
2015-07-14 22:21:48.237407
Connection 66919 timed out, server is dropping the connection.
2015-07-14 22:21:48.237444
Open connections are:
[66246, 12012, 6069]
Closing connection 66919.
Total time online:
0:30:00.000143
Time between connection start and last message received:
0:00:00
Number of open connections: 3
可以看出,66919 是 "closed" 两次,间隔为 30 分钟。有什么想法吗?
另一个连接 3358 被关闭的例子,当假设没有更多打开的连接时(再次关闭两次,间隔 30 分钟):
Open connections are:
[7046, 16287]
2015-07-15 11:01:13.604125
New connection. ID: 3358
Total number of open connections: 3
2015-07-15 11:01:28.429574
Open connections are:
[7046, 3358, 16287]
Closing connection 3358.
Total time online:
0:00:14.825568
Time between connection start and last message received:
0:00:00
Number of open connections: 2
Open connections are:
[7046, 16287]
--
Open connections are:
[]
2015-07-15 11:31:13.629530
Connection 3358 timed out, server is dropping the connection.
2015-07-15 11:31:13.629586
Open connections are:
[]
Closing connection 3358.
Total time online:
0:30:00.025556
Time between connection start and last message received:
0:00:00
Number of open connections: 0
Open connections are:
[]
有人指出我不应该在force_close
中调用common_close
,因为on_close
会被self.close()
调用,但是on_close()
不会' 被 self.close()
调用。
看起来两个重复的 id 正好相隔 30 分钟。这只能说明一件事,当连接被关闭时,另一个定时器被调度,第二个定时器在超时时打印重复的日志。从您的代码判断,这只会发生在 on_message
.
您的客户端如何处理连接关闭?客户端是否有可能在收到 FIN 后立即向服务器发送消息?
在龙卷风源代码中,
# Give the client a few seconds to complete a clean shutdown,
# otherwise just close the connection.
self._waiting = self.stream.io_loop.add_timeout(
self.stream.io_loop.time() + 5, self._abort)
所以服务器给客户端5秒的时间来终止连接,如果客户端在这5秒内向服务器发送消息,可能会出问题。
这只是我的猜测。
common_close
被调用两次,但连接仅超时一次。在您的第一个示例中,66919 在 21:51 处关闭,因为客户端完全关闭了连接(通过 on_close
),然后由于超时再次在 22:21 处关闭。连接对象即使在关闭后仍然存在。连接未打开;只有超时仍然有效。如果 on_close
(或 common_close
)处于活动状态,您需要删除超时。
您还应该在 open()
开始第一次超时而不是等待 on_message()
,并且 force_close()
应该将 self.timeout
设置为 None。
因为 Tornado 4.1 on_close()
将被 self.close()
调用。