Message341690
I do not know I still have the issue since I have circumvented the problem. I have been using Python3.4, I think it was one of the earliest asyncio implementations. The way it can be reproduced is as following:
1) There are lots of active TCP connections connected to asyncio server (300-400 of them)
2) One of the clients close connection ungracefully(without sending a FIN)
3) We have a PING/PONG mechanism in the server (similar to http keep-alive), we call transport.close() on the socket if pong is not received within an interval.
connection_lost() event is never gets called for the socket. This is not happening all the time, this is a random issue, the key here is to disconnect client without sending a FIN and there is outgoing buffer for client.
Above is all I got.
Thanks! |
|
Date |
User |
Action |
Args |
2019-05-07 07:22:29 | Sümer.Cip | set | recipients:
+ Sümer.Cip, gvanrossum, vstinner, yselivanov, anthonypjshaw |
2019-05-07 07:22:29 | Sümer.Cip | set | messageid: <1557213749.14.0.0809586294593.issue26278@roundup.psfhosted.org> |
2019-05-07 07:22:29 | Sümer.Cip | link | issue26278 messages |
2019-05-07 07:22:28 | Sümer.Cip | create | |
|