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.