-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
CommunicationsException: The last packet successfully received from the server was 901,702 milliseconds ago. The last packet sent successfully to the server was 901,705 milliseconds ago. #5889
Comments
你这个看上去db操作频率很低,不然也不会连接等到15分钟超时。 |
我们的QPS其实很高。按我们的如下配置,理论上,每次借用连接时,如果其空闲时间超过60S,会进行一次探测;而且每隔60S也会对空闲时间超过300S的进行关闭,这样不应该会借用到空闲900S的连接吧。不知道我这么理解对不对? |
|
我也有这类问题,请问怎么解决呢,我的问题是#5920 |
除非每台机器配置的cpu核数很多,或者你有耗时很长的单条sql或db事务,否则用不了这么多的连接,可以找台机器netstat动态监控一下你应用创建的数据库连接数。 |
此类问题过一段时间就会冒出来,如果看过wiki配置说明,应该知道连接保活的前提条件是keepAlive选项设置为true |
@lizongbo 建议下一个版本把keepAlive这个选项默认值改为true |
直接改为true会有130个单测失败,周末温少会发1.2.23,等发完版本之后再来调整 |
大佬好,我们用Druid一直偶发
CommunicationsException
,升级到最新的1.2.22仍然出现,辛苦帮看下我们哪的姿势不对,万分感谢。dbtype:MySQL
dbversion:5.7
druid verion:1.2.22
配置如下:
异常信息如下:
The text was updated successfully, but these errors were encountered: