springboot启动报错The last packet successfully received from the server was 343 milliseconds ago

最新推荐文章于 2024-08-18 17:37:54 发布

榴莲啊千层

最新推荐文章于 2024-08-18 17:37:54 发布

阅读量1.8k

点赞数

文章标签： spring boot 数据库 mysql

本文链接：https://blog.csdn.net/qq_42538451/article/details/126848604

版权

完整错误如下

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.Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors
springboot+hibernate启动同时报以上两种错，查看mysql连接配置

原连接设置

spring.datasource.url = jdbc\:mysql\://127.0.0.1\:3336/ess?characterEncoding\=utf8&useSSL\=false

新连接设置

spring.datasource.url = jdbc\:mysql\://127.0.0.1\:3336/ess?characterEncoding\=utf8&useSSL\=true

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

榴莲啊千层

关注关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
2
评论
复制链接

分享到 QQ

分享到新浪微博

扫一扫

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

隔壁老瓦的专栏

10-12

1216

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

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个小时没有从服务器上接

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

The last packet sent successfully to the server was XXX milliseconds ago解决方案（Springboot+Mysql5.7）

weixin_38203586的博客

09-01

3334

The last packet sent successfully to the server was XXX milliseconds ago解决方案（Springboot+Mysql5.7）

The last packet successfully received from the server was milliseconds ago

热门推荐

mingrenc的博客

08-17

3万+

遇到这个问题查阅很多博客，基本上大同小异，但是都于事无补。参考文章：https://blog.csdn.net/frankcheng5143/article/details/50589264 可以移步到此查看。网上的方案： 1.将mysql服务器的wait_timeout设置为无穷大，保证永不超时（不知道可以不，不建议采用（事实上没什么用，有文章说对5.0之前的mysql适用），像这样 ...

kettle问题：The last packet successfully received from the server was 156 milliseconds ago.

Letitia1208的博客

04-23

2766

在使用kettle时遇到MySQL数据库连接问题： 1.Navicat可以连接到目标MySQL库，说明不是数据库权限的问题。 2.用kettle可以连接其他同版本MySQL库，说明也不是jar包的问题。最终，尝试过重启电脑，删除kettle文件重装，替换jar包等各种办法之后，才发现问题在.kettle文件夹里面：这是出问题时.kettle文件夹下面的文件，比正常文件多了一些东西。个人的解决办法： 1.备份 kettle.properties 文件，这是平时用的连接资源库的信息 2.删除.kett

【MySQL之轨迹】The last packet successfully received from the server was xxx milliseconds ago 连接超过 8 小时失效

Ice__Clean的博客

05-25

2726

数据库连接闲置 8 小时的解决方法之一：定时更新数据库连接池中的连接，使用了 jdk8 的新日期获取方式，通过连接创建的时间与当前使用的时间之差是否超时判断是否更新连接池

The last packet successfully received from the server was 59,866 milliseconds ago. The last packet

mt23

09-11

1027

com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure The last packet successfully received from the server was 59,866 milliseconds ago. The last packet sent successfully ...

使用连接池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 4 milliseconds ago.

qq_37144511的博客

05-11

1171

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

The last packet successfully received from the server was 596,688 milliseconds a

qq123zhz的专栏

09-05

809

转载： The last packet successfully received from the server was 596,688 milliseconds ago. 后来查了一些资料，才发现遇到这个问题的人还真不少，大部分都是使用连接池方式时才会出现这个问题，短连接应该很难出现这个问题。这个问题的原因： MySQL服务器默认的“wait_timeout”是28800秒即8小时...

The last packet successfully received from the server was 0 millis

qq_42521108的博客

04-10

815

备注：本人遇到并处理的方式。

The last packet successfully received from the server was 39,900 milliseconds ago问题解决

weixin_30784501的博客

06-25

463

1，之前用Mysql或者mycat的时候都没有这个问题。后来改为haproxy+keepalived+mycat后出现这个问题 2，网上查了很多说法，我按照网上说的改了 datasource: url: jdbc:mysql://192.168.0.206:8067/NOVADB?useUnicode=true&characterEncoding=utf8&a...

The last packet successfully received from the server was 30,516,920 milliseconds ago.

StrideBin的博客

06-22

1万+

今天早上发了一笔交易发现服务器上报错可见这笔交易是9点半左右发出的入库的时候发现连接已经断掉,第一反应先计算了一下断掉的时间30516920/3600/1000 = 8.4769222222222. 大概就是半夜一点钟断掉的.我又去查了一下上一次启动项目的时间,发现现在的进程已经不是我上一次启动的进程了,也就是说中间肯定有人启过,于是我去查了一下Jenkins .果然有人动过.是不是

The last packet successfully received from the server was 8,098,360 milliseconds ago.

蓝天之枫

01-16

3604

线上环境凌晨5分有个定时任务没执行，查看日志发现报错 The last packet successfully received from the server was 8,098,360 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago. 这个意思是说从服务器成...

2021-01-27

weixin_45686043的博客

01-27

144

问题描述： org.apache.ibatis.exceptions.PersistenceException: ### Error querying database. Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 8,210 millisecond

如何解决MySQL报错"The last packet successfully received from the server was X milliseconds ago"？

02-27

当MySQL报错"The last packet successfully received from the server was X milliseconds ago"时，这通常是由于连接超时引起的。解决这个问题的方法有以下几种： 1. 检查网络连接：首先确保网络连接正常，可以尝试...