<Closing connections idle longer than 60000 MILLISECONDS> <Closing expired connections>

本文轉載自查看原文 2017-12-07 14:25 8677 OSS

日志信息如下:

2017-07-05 18:28:34 -18705 [idle_connection_reaper] DEBUG   - Closing expired connections
2017-07-05 18:28:34 -18723 [idle_connection_reaper] DEBUG   - Closing connections idle longer than 60000 MILLISECONDS
2017-07-05 18:28:39 -23724 [idle_connection_reaper] DEBUG   - Closing expired connections
2017-07-05 18:28:39 -23724 [idle_connection_reaper] DEBUG   - Closing connections idle longer than 60000 MILLISECONDS

解決辦法:

　　在ossClient使用之后應該立即關閉,ossClient.shutdown();

免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。

猜您在找 項目讀取數據，一直出現 Closing connections idle longer than 30 SECONDS，卡死現象 socket 關閉但端口占用問題 Bind: Address Already in Use Or How to Avoid this Error when Closing TCP Connections 程序重復報more than 'max_user_connections' active connections問題解決

python中with及closing skip connections TP5報錯 User qdm813229266 already has more than 'max_user_connections' active connections 解決辦法 max_connections Max_used_connections Mysql 的異常：The last packet successfully received from the server was 90 milliseconds ago. The last packet sent successfully to the server was 43,603,303 milliseconds ago. is longer than the server con Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.