java.io.EOFException: Can not read response from server. Expected to read 4 bytes
查看後臺kibana日誌，發現訪問數據庫偶爾會出現異常： 網上有很多類似的案例，查了下，原因如下： 經過查詢，應該是連接池的連接一段時間沒有活動筋骨，mysql服務端會單方面斷開這個連接。客戶端繼續使用這個殭屍連接就會出錯。 查看mysql實例的配置my.cnf，其中wait-timeout參數設置爲20秒，由於新上線還沒多少客戶使用，所以這個設置對於這種不活躍的場景太短了。直接刪除這個配置，my
相關文章
- 1. mysql Can not read response from server. Expected to read 4 bytes 異常
- 2. Caused by: java.io.EOFException: Can not read response from server的解決方案
- 3. Unable to read additional data from server sessionid 0x0
- 4. while opening read connection: jdbc:mysql message from server: Host is not allowed to connect to t
- 5. Could not retrieve transaction read-only status from server
- 6. java.sql.SQLException: Could not retrieve transaction read-only status from server
- 7. 'Connection broken: IncompleteRead(1482 bytes read, 2614 more expected)', IncompleteRead(1482 bytes
- 8. happybase(TSocket read 0 bytes)
- 9. Can you read this?
- 10. fatal: Could not read from remote repository.
- 更多相關文章...
- • ASP Read 方法 - ASP 教程
- • ASP Response 對象 - ASP 教程
- • Docker容器實戰(一) - 封神Server端技術
- • Java Agent入門實戰（一）-Instrumentation介紹與使用
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
歡迎關注本站公眾號,獲取更多信息
相關文章
- 1. mysql Can not read response from server. Expected to read 4 bytes 異常
- 2. Caused by: java.io.EOFException: Can not read response from server的解決方案
- 3. Unable to read additional data from server sessionid 0x0
- 4. while opening read connection: jdbc:mysql message from server: Host is not allowed to connect to t
- 5. Could not retrieve transaction read-only status from server
- 6. java.sql.SQLException: Could not retrieve transaction read-only status from server
- 7. 'Connection broken: IncompleteRead(1482 bytes read, 2614 more expected)', IncompleteRead(1482 bytes
- 8. happybase(TSocket read 0 bytes)
- 9. Can you read this?
- 10. fatal: Could not read from remote repository.