windows解决:mysql连接报错“The last packet successfully received from the server was xxx milliseconds ago”.

优化MySQL连接超时设置：my.ini配置教程

最新推荐文章于 2024-10-31 15:32:24 发布

原创最新推荐文章于 2024-10-31 15:32:24 发布 · 1.6w 阅读

20 ·

CC 4.0 BY-SA版权

文章标签：

#mysql #数据库

在系统目录下找到my.ini配置文件，以记事本方式打开

然后找到[mysqld]

将下面两句添加上去，保存

wait_timeout=604800
interactive_timeout=31536000

最后以管理员身份打开命令窗口，重启mysql服务即可

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

dd_ddesd

关注关注

11
点赞
踩
20

收藏

觉得还不错? 一键收藏
0
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

The last packet successfully received from the server was 4,758 milliseconds ago

隔壁老瓦的专栏

10-12

2267

Thelastpacketsuccessfullyreceivedfromtheserverwas4,758millisecondsago.Thelastpacketsentsuccessfullytotheserverwas4,758millisecon dsago.;nestedexceptioniscom.mysql.jdbc.exceptions.jdbc4.CommunicationsException:Communicationslin...

doris Communications link failureThe last packet successfully received from the server was 10057

最新发布

u011250186的博客

09-15

395

doris jdbc连接错误。

参与评论您还未登录，请先登录后发表或查看评论

c3p0连接数据库超时问题:The last packet successfully received;The last packet sent successfully to the server

沧笙踏歌的博客

04-19

3854

问题描述 java.sql.SQLException: The last packet successfully received from the server was 36,483,780 milliseconds ago. The last packet sent successfully to the server was 36,483,781 milliseconds ago. is ...

springboot hikari数据库连接池死链出现异常

wangjun5159的专栏

05-28

5062

最近用户反应系统很慢，登录时，经常超时、无反应，查看log出现上述两种异常，异常情况1 The last packet successfully received from the server was 995,202 milliseconds ago. The last packet sent successfully to the server was 995,202 milliseconds ago. at com.mysql.cj.jdbc.exceptions.SQLError.crea

由于数据库连接池的原因，造成CommunicationsException: Communications link failure，遇到这样的坑，记录下来

纯洁的大白

11-27

3044

一、先上日志报错日志报错太长，就截图了能找到错误的原因，关键在这句：The last packet successfully received from the server was 1,996,637 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago. 二、问...

mysql重连，连接丢失：The Last Packet Successfully Received From the Server

mauersu

07-15

794

源：http://nkcoder.github.io/ 评： 1.1 错误信息： Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 20,820,001 milliseconds ago....

mysql连接池报错:The last packet successfully received from the server was XXXXX milliseconds ago

诸葛小猿

12-10

2万+

具体报错信息 0:Communications link failure The last packet successfully received from the server was 87,537,289 milliseconds ago. The last packet sent successfully to the 报错日志解释从服务器成功接收的最后一个数据包是87,537,289（24.3小时）毫秒前。最后一个成功发送到服务器的数据包是0毫秒前。说明这个连接已经24个小时没有从服务器上接

The last packet successfully received from the server was 4 milliseconds ago.

qq_37144511的博客

05-11

2237

它表明 JDBC 客户端与 MySQL 数据库服务器之间的通信链接在某个点突然中断，但在错误消息给出的时间点，客户端和服务器之间仍然有数据包交换的记录。1、在配置文件my.cnf中设置max_connections的值（重启后生效）找到max_connections一行，修改为（如果没有，则自己添加）报这个错误大多数是因为数据库连接的问题，有可能网络，有可能连接数。（最大连接数，这个参数实际起作用的最大值为16384）###2、修改临时连接数（不需要重启mysql）说明连接已经满了，3000满足不了需求。

使用连接池druid报错The last packet successfully received from the server was XXX milliseconds ago.（实测解决）

09-15

这个报错通常是由于数据库连接超时引起的。可以尝试以下方法解决： 1. 检查数据库的最大连接数配置，确保连接池中有足够的连接可用。 2. 增加数据库连接超时时间，可以在连接池配置中设置"maxWait"或"maxWaitMillis...

The last packet successfully received from the server was 244,252 milliseconds ago. The last packet sent successfully to the server was 244,252 milliseconds ago.

07-17

这看起来是关于MySQL连接超时错误的问题，具体错误是“last packet successfully received from the server was xxx milliseconds ago”。从系统级指令中，我需要： - 使用中文回答 - 结构清晰，帮助用户逐步解决...

达梦数据库连接mysql失败报错：错误消息: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

07-22

嗯，用户遇到了达梦数据库连接时的"Communications link failure"错误。这个错误通常意味着客户端无法与数据库服务器建立网络连接，需要系统性地排查多个环节。首先想到网络层的问题。用户可能遇到防火墙阻断、IP...

The last packet successfully received from the server was 10,014 milliseconds ago. The last packet sent successfully to the server was 10,021 milliseconds ago.

03-28

嗯，用户遇到了服务器连接超时或网络延迟的问题，特别是在使用MySQL时，数据包收发延迟达到毫秒级。我需要根据提供的引用和知识来整理解决方案。首先，用户提到了Linux连接超时参数，引用[1]指出sysctl中的某个...

he last packet successfully received from the server was 10,016 milliseconds ago

07-28

引用\[1\]:The last packet successfully received from the server was 343 milliseconds ago. The last packet sent successfully to the server was 336 milliseconds ago. 引用\[2\]:问题： Java项目启动，mysql...

mysql问题：‘The last packet successfully received from the server was xxx milliseconds ago‘

weixin_43103956的博客

03-01

3575

（2）从报错信息来看，这里设置的超时是10000毫秒，debug mysql-connector源码，发现有socketTimeout参数的值正好是10000，于是在datasource.url后面socketTimeout参数配置，重启测试发现能被正确识别，正常。1.springboot + druid + mysql 在查询某些比较耗时的sql会报错。（1）sql上增加分页限制不会报错；

The last packet successfully received from the server was xxx milliseconds ago. The last packet sen

Muxiu

06-02

2737

【代码】The last packet successfully received from the server was xxx milliseconds ago. The last packet sen。

Communications link failure，The last packet successfully received from the server was *** millisecon

热门推荐

阿里旺仔。

06-01

2万+

最近做测试，发现Mysql 过一段时间会无法连接，导致数据库数据不一至，极其郁闷。下面是转一哥门的使用Connector/J连接MySQL数据库，程序运行较长时间后就会报以下错误： Communications link failure，The last packet successfully received from the server was *** millisec

The last packet successfully received from the server was milliseconds ago

levi_work的博客

03-11

848

修改mysql的wait_timeout，修改spring数据源配置，增加maxWait（要比数据库wait_timeout小）、testOnBorrow=true、queryTimeout等配置，在datasource.url后面增加autoReconnect=true配置。从报错信息来看，这里设置的超时是10000毫秒，然后把mysql-connector源码下载下来debug了一下，发现有socketTimeout参数的值正好是10000，然后尝试在spring数据源配置上增加次配置依旧不行。

数据库连接超时：“The last packet successfully received from the server was xxx milliseconds ago”...

weixin_30770783的博客

01-21

1万+

产生的原因：应用方的数据库连接有效期时间，大于数据库自己设置的有效期。解决方案：一、修改druid配置（如果使用druid的话） spring.datasource.druid.validationQuery=select 1 spring.datasource.druid.testWhileIdle=true spring.datasource.druid.te...

The last packet successfully received from the server was 5,627,630 milliseconds ago.

Eric_ChenXiao的博客

10-31

1764

客户端连接池中的连接与MySQL server端连接池的连接是一一对应的，超出wait_timeout配置的时间未连接过，则服务端将对应的连接销毁，这时候客户端是不知道的。客户端应用的连接池中的连接最后一次收到MySQL server的相应是xxx毫秒之前；超过生命时长的，空闲的直接驱逐，非空闲的标记，下次获取时驱逐。服务端到期销毁连接之前，客户端就先销毁对应的连接,也就是客户端销毁连接的时间要小于wait_timeout配置的时间。下次客户端再去进行连接的时候，就会出现上面的错误。