-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
muduo-master/examples/asio/chat 里面的./asio_chat_client 进入死循环 #131
Comments
基本上,只要数据收发还正常的情况下,如果把 nginx 重启,就会重现。 |
为什么你认为这是muduo的问题,而不是nginx的问题? |
现在还没有抓包分析,不过 TcpClient 的重连频率还是很高,基本和死循环一样。 |
从你给的log看,重连的间隔有0.5s。这有什么问题? |
传图 |
上图上不去,只能上客户端 log 了。 |
因为服务器端主动关闭了连接,而每次客户端也析构了连接对象,导致 Connector 类每次都使用 |
因为每次连接都成功了,客户端没有进入连接失败,所以 客户端作死连接,服务器拼命关闭。 |
我认为问题出在server端,TcpClient没有问题。 |
muduo-master/examples/asio/chat
里面的./asio_chat_client 进入死循环。看到客户端表现如下,不断的重新连接。
20150323 10:03:38.336293Z 6660 INFO 169.254.10.12:34128 -> 169.254.10.12:26888 is UP - client.cc:53
20150323 10:03:38.336324Z 6660 INFO 169.254.10.12:34128 -> 169.254.10.12:26888 is DOWN - client.cc:53
20150323 10:03:38.857066Z 6660 INFO TcpClient::connect[ChatClient] - Reconnecting to 169.254.10.12:26888 - TcpClient.cc:178
20150323 10:03:38.857196Z 6660 INFO 169.254.10.12:34130 -> 169.254.10.12:26888 is UP - client.cc:53
20150323 10:03:38.857328Z 6660 INFO 169.254.10.12:34130 -> 169.254.10.12:26888 is DOWN - client.cc:53
20150323 10:03:38.857345Z 6660 INFO TcpClient::connect[ChatClient] - Reconnecting to 169.254.10.12:26888 - TcpClient.cc:178
测试过程如下:
,重新把 nginx 起来,asio_chat_client 再发送数据进入了死循环。
也就是过了 nginx 和 asio_chat_server 的检查时间才能正常。
The text was updated successfully, but these errors were encountered: