The last packet successfully received from the server was 751 milliseconds ago. 项目启动报错

最新推荐文章于 2024-08-10 11:58:24 发布

骑着王八看大海

最新推荐文章于 2024-08-10 11:58:24 发布

阅读量792

点赞数

文章标签： mysql 数据库 spring

本文链接：https://blog.csdn.net/YM550/article/details/123565603

版权

1检查mysql的服务是否启动可以通过Navicat 连接进行测试；如果连接不上就是mysql服务的问题

2检查这个url路径 useSSL这个参数改为false，改为true会报错

jdbc:mysql://localhost:3306/data_reporting?useUnicode=true&characterEncoding=utf8&zeroDateTimeBehavior=convertToNull&useSSL=false&serverTimezone=GMT%2B8

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

骑着王八看大海

关注关注

0
点赞
踩
0

收藏

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

分享到 QQ

分享到新浪微博

扫一扫

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

隔壁老瓦的专栏

10-12

1244

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

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

mt23

09-11

1037

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 ...

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

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

Letitia1208的博客

04-23

2774

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

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 sent successfully to the server was 10,001 milliseconds ago深入分析及解决方案

热门推荐

qq_21128741的博客

02-25

4万+

2com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure 3 The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. 宿主机ping不通Linux

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

Ice__Clean的博客

05-25

2765

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

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

蓝天之枫

01-16

3630

线上环境凌晨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. 这个意思是说从服务器成...

The last packet successfully received from the server was 11,226 milliseconds ago.

stujike123456的博客

08-13

3745

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 11,226 milliseconds ago. Caused by: java.net.Socket...

The last packet successfully received from the server was 4,371,572 milliseconds ago. The last pack

把酒问天专栏

08-31

1399

1.1 错误信息: The last packet successfully received from the server was 4,371,572 milliseconds ago. The last packet sent successfully to the server was 18,902 milliseconds ago. at sun.reflect.NativeCo...

The last packet successfully received from the server was 1,266,537 milliseconds ago. The last pack

java1993666的博客

02-23

1万+

最近接手一个项目，由于该项目对mysql数据库使用频率不是很高，线上每天都会报几十条数据库连接失效的错误信息，刚开始没空处理这个错误，连接失效超时后会继续建立有效连接，不会影响正常的业务。今天抽空处理下这个错误，简单做下总结： 1、线上错误的日志信息如下： 2019-02-23 09:49:35:872 d.s.Statement 149 [ERROR] {conn-10345, stmt-4...

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

weixin_30770783的博客

01-21

9551

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

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

龙飞的博客

07-21

2742

相关url链接加入一些参数解决，如下所示。

mysql The last packet successfully received from the server was XXX seconds ago

beyondlpf的专栏

04-02

1万+

用JDBC去连MYSQL的时候，报错The last packet successfully received from the server was XXX seconds ago 防火墙已经打开这个IP，仍然报错，最终看了这篇文章： iptables关于MTU数据包问题（内网VPN防火墙策略） 2012-11-21 11:28:22| 分类： IPTABLE

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

赶路人儿

05-06

4万+

关于MySQL连接超时问题，估计很多人都遇到过：大致情形都是这样，开发测试时程序都是正常的，一到第二天就出先莫名错误，比如在我的项目中使用了多数据源，其中有一个数据源仅仅供查询使用，所以使用次数很少。当出现了超时错误，一般错误日志如下： Communications link failure The last packet successfully received from the serv

Communications link failure:The last packet successfully received from the server was 0 millisecond

LookingTomorrow的博客

12-03

1万+

出现这种错误的大致情况如下： 1、数据库连接长时间未使用，断开连接后，再去连接出现这种情况。这种情况常见于用连接池连接数据库出现的问题 2、数据库连接的后缀参数问题针对上述两种情况，解决方案如下 1、修改MySQL的参数,my.cnf位于/etc目录下，修改完成后，重启mysql wait_timeout最大为31536000即1年，在my.cnf中加入： [mysqld] wait_timeout=31536000 interactive_timeout=31536000 2、连接数

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

04-09

The last packet successfully received from the server was 2 milliseconds ago. The last packet sent refers to the most recent packet that was sent from the client to the server. It indicates the time ...