2021-01-27

最新推荐文章于 2023-09-07 13:13:07 发布
最新推荐文章于 2023-09-07 13:13:07 发布
阅读量131 收藏
点赞数
分类专栏： mybatis错误 文章标签： mybatis
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_45686043/article/details/113268164
版权

问题描述：

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 milliseconds ago.  The last packet sent successfully to the server was 8,204 milliseconds ago.
### The error may exist in com/tiansun/dao/UserMapper.xml
### The error may involve com.tiansun.dao.UserDao.getUserList
### The error occurred while executing a query
### Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet successfully received from the server was 8,210 milliseconds ago.  The last packet sent successfully to the server was 8,204 milliseconds ago.

	at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:30)
	at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:149)
	at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:140)
	at org.apache.ibatis.binding.MapperMethod.executeForMany(MapperMethod.java:147)
	at org.apache.ibatis.binding.MapperMethod.execute(MapperMethod.java:80)
	at org.apache.ibatis.binding.MapperProxy.invoke(MapperProxy.java:57)
	at com.sun.proxy.$Proxy4.getUserList(Unknown Source)
	at com.tiansun.dao.UserDaoTest.test(UserDaoTest.java:17)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:33)
	at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:230)
	at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:58)
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet successfully received from the server was 8,210 milliseconds ago.  The last packet sent successfully to the server was 8,204 milliseconds ago.
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
	at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116)
	at com.mysql.jdbc.ExportControlled.transformSocketToSSLSocket(ExportControlled.java:105)
	at com.mysql.jdbc.MysqlIO.negotiateSSLConnection(MysqlIO.java:4664)
	at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1354)
	at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2336)
	at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2369)
	at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2153)
	at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:792)
	at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
	at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:381)
	at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:305)
	at java.sql.DriverManager.getConnection(DriverManager.java:664)
	at java.sql.DriverManager.getConnection(DriverManager.java:208)
	at org.apache.ibatis.datasource.unpooled.UnpooledDataSource.doGetConnection(UnpooledDataSource.java:221)
	at org.apache.ibatis.datasource.unpooled.UnpooledDataSource.doGetConnection(UnpooledDataSource.java:216)
	at org.apache.ibatis.datasource.unpooled.UnpooledDataSource.getConnection(UnpooledDataSource.java:95)
	at org.apache.ibatis.datasource.pooled.PooledDataSource.popConnection(PooledDataSource.java:422)
	at org.apache.ibatis.datasource.pooled.PooledDataSource.getConnection(PooledDataSource.java:89)
	at org.apache.ibatis.transaction.jdbc.JdbcTransaction.openConnection(JdbcTransaction.java:138)
	at org.apache.ibatis.transaction.jdbc.JdbcTransaction.getConnection(JdbcTransaction.java:60)
	at org.apache.ibatis.executor.BaseExecutor.getConnection(BaseExecutor.java:336)
	at org.apache.ibatis.executor.SimpleExecutor.prepareStatement(SimpleExecutor.java:85)
	at org.apache.ibatis.executor.SimpleExecutor.doQuery(SimpleExecutor.java:62)
	at org.apache.ibatis.executor.BaseExecutor.queryFromDatabase(BaseExecutor.java:324)
	at org.apache.ibatis.executor.BaseExecutor.query(BaseExecutor.java:156)
	at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:109)
	at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:83)
	at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:147)
	... 28 more
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1959)
	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1514)
	at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
	at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
	at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1072)
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397)
	at com.mysql.jdbc.ExportControlled.transformSocketToSSLSocket(ExportControlled.java:90)
	... 59 more
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:397)
	at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:302)
	at sun.security.validator.Validator.validate(Validator.java:260)
	at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
	at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
	at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1496)
	... 67 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141)
	at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126)
	at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280)
	at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:392)
	... 73 more

解决方案：

mybatis-config.xml

<?xml version="1.0" encoding="UTF8" ?>
<!DOCTYPE configuration
        PUBLIC "-//mybatis.org//DTD Config 3.0//EN"
        "http://mybatis.org/dtd/mybatis-3-config.dtd">
<configuration>
<!-- 核心配置文件   -->
    <environments default="development">
        <environment id="development">
            <transactionManager type="JDBC"/>
            <dataSource type="POOLED">
                <property name="driver" value="com.mysql.jdbc.Driver"/>
                <property name="url" value="jdbc:mysql://127.0.0.1:3306/demo?useSSL=true&amp;useUnicode=true&amp;characterEncoding=utf8"/>
                **//把 useSSL=true   改成 false 即可运行成查出数据**
                <property name="username" value="root"/>
                <property name="password" value="root"/>
            </dataSource>
        </environment>
    </environments>
<!--    没一个mapper 都需要在mybatis 核心文件 注册一下-->
    <mappers>
        <mapper resource="com/tiansun/dao/UserMapper.xml" />
    </mappers>
</configuration>
Moriiiiiiii
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
数据库连接超时：“The last packet successfully received from the server was xxx milliseconds ago”...
weixin_30770783的博客
01-21 9102
产生的原因：应用方的数据库连接有效期时间，大于数据库自己设置的有效期。 解决方案： 一、修改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 xx milliseconds ago. The last packet sent
【欢迎关注公众号：冬瓜白】
08-27 4355
同组同事遇到的问题。 完成异常信息如下： The last packet successfully received from the server was xxx milliseconds ago. The last packet sent successfully to the server was xxx milliseconds ago. ### Error querying d...
mysql链接错误The last packet successfully received from the server was xxx milliseconds ago解决方案
weixin_44487203的博客
03-17 2万+
线上项目偶尔出现错误，这个错误发现是在项目无人操作一段时间后就产生，如果有人操作，那就不会出现。
深度解析数据库连接The last packet successfully received from the server was *xxx* milliseconds ago
雨潇的专栏
08-16 2万+
相信很多人都遇到过这个问题，看到提示信息，或许大家都明白这不就是获取到的数据库连接超时了嘛，没错，问题的本质也的确如此，常见的解决办法也很简单，比如说从数据库连接池中获取连接的时候判断下连接状态是否正常，这样就可以避免此类问题的发生，如果都是此问题，那么就不会再有本文来赘述问题和解决方案，下面一起来看看造成该问题的几个原因和解决方法。 1.从连接池获取到超时的连接 从数据库连接池获取到超时的连接，目前这种情况大多数数据库连接池中间件都有相应的处理策略，一种是定期扫描连接池中的连接，探测到失效连接后剔除功能，
彻底解决"The last packet successfully received from the server was * milliseconds ago"问题
待风宜月
05-03 3万+
1.修改mysql 的 wait_timeout参数（和interactive_timeout一起） 不推荐 2.如果用hibernate.必须手动配置连接池，最好是用c3p0连接池。如果不配，会使用内置连接池。内置连接池的8小时断开问题不知道hibernate开发者怎么还不解决！ 3.干脆不用hibernate,spring的jdbc template+自己配连接池就非常好。
nessus2021-01-27最近漏洞更新包
01-27
nessus2020-11-14最近漏洞更新包，以把插件包上传到服务器后， 执行/opt/nessus/sbin/nessuscli update 插件包文件路径
tampermonkey-backup-chrome-2021-11-27T13-18-01-624Z.zip
11-27
下载后通过Tampermonkey直接导入即可使用。
tampermonkey-backup-chrome-2021-01-27T09-36-27-548Z.zip
01-27
Tampermonkey脚本文件
CVE-2021-26121
02-13
= 4.12.x（最新） 日期：2020-01-08 12:49 CVE：CVE-2021-26121披露时间表2020-01-26 –发送给CS-Cart开发团队2020-01-27 – CS-Cart开发团队收到通知2020-02-10 – cs-cart的回应不是安全漏洞，限制了商店管理员的...
tampermonkey-backup-chrome-2021-11-27T01-27-17-766Z.zip
11-27
配置过的油猴插件
解决MySQL报错：“The last packet sent successfully to the server was 0 milliseconds ago.”
最新发布
培根芝士的专栏
09-07 2万+
方法就是将mysql回收空闲连接的时间变长，mysql默认回收时间是8小时，可以在mysql目录下的my.cnf中增加下面配置，将时间改为1天。之所以出现异常，是由于数据库回收了连接，而系统的缓冲池不知道，继续使用被回收的连接所致的。wait_timeout=86400 //加上这一句。
kettle数据库连接问题
kokool的博客
05-04 1822
实验环境： mysql server版本是5.7+ jdk是1.8 另外我在kettle 的lib文件夹下放入了相应版本的mysql-connect-jre包（这个也是要跟你的mysql server版本对应上，一般都是5.1.17以上） 问题的可能原因： mysql的版本是最新的8（本博客不解决这个问题） 主机名称有误（也即地址有误） 数据库名写错了（即没有这个数据） 总结：粗心大意 地址错误的提示日志： 就下面这一句是核心，有的会说地址冲突，不过你单机环境怎么可能会有这个问题 The last p
The last packet successfully received from the server was 11,226 milliseconds ago.
stujike123456的博客
08-13 3674
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 sent successfully to the server was 0 milliseconds ago. The driver has not receiv
热门推荐
Huang405267467的博客
07-07 4万+
注：此文章是在mysql8版本的前提下编写的。在我们使用springcloud在连接mysql数据库时，有时会碰到如下这种异常： 为此我上网查了不少资料，在这里小总结一下：1. 连接url是否正确（自己看看useSSL是否为false）：2.数据库服务是否打开：找到MySql服务：3.网上最多解决的等待时间问题：（wait_timeout)我使用的mysql版本为 8.0.27 ，在用网上的修改my.ini配置文件时 mysql会直接报错，启动不了，即使临时修改wait_timeout时间，也是一样会报
mysql数据库连接报错The last packet sent successfully to the server was 0 milliseconds ago. The drive
flyf000的博客
08-16 1万+
mysql数据库连接报错The last packet sent successfully to the server was 0 milliseconds ago. The drive
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
Communications link failure
高强的博客
07-13 281
没有启动mysql服务。com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failureThe last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any ...
C3P0连接池详解及配置
wangking:开源世界，人人都用上了正版啦。。。
08-28 2万+
我也来续一下：数据库连接是一个耗费大量资源且相当慢的操作，所以为了提高性能和连接速度，诞生了连接池这样的概念。在多用户并发操作过程中，连接池尤为重要。它是将那些已连接的数据库连接存放在一个容器里（连接池），这样以后别人要连接数据库的时候，将不会重新建立数据库连接（这样蜗牛的慢动作谁都受不了的），他会直接从连接池里取出可用的连接，用户使用完毕后，连接又重新回到连接池中。注意：连接池里
MySQL数据库提示：Communications link failure，The last packet successfully received...
苳眠の菜鸟
10-08 8335
       Last modified：2013-10-08 14:16:47      **********************************************         web网站使用MySQL数据库，今天突然报以下错误：       Communications link failure，The last packet successfully re...
结果是这样的，没有根据id排：start_date end_date 0 2020-01-15 2020-04-27 1 2020-09-30 2020-10-10 2 2021-02-07 2021-02-22 3 2021-03-06 2021-03-24 4 2020-01-21 2020-03-03 .. ... ... 639 2021-03-09 2021-03-18 640 2021-03-24 2021-04-01 641 2020-01-12 2020-04-19 642 2021-02-09 2021-02-18 643 2020-01-18 2020-03-09
06-03
如果你想根据企业id对结果进行排序，可以在输出结果之前加上一行代码： ```python result = result.sort_values(by=['id']) ``` 此代码将会根据id对结果进行排序，使得每个企业的结果排在一起。完整的代码如下： ```python mean = DataFrame.groupby(['id'])['amount'].mean() # 列出每个企业用电量低于均值时间超过一周的时间段，标记起始时间和结束时间，省略中间时间 filtered_data = DataFrame[DataFrame['amount'] < DataFrame['id'].map(mean)] filtered_data['date'] = pd.to_datetime(filtered_data['date']) filtered_data['diff'] = filtered_data.groupby('id')['date'].diff().dt.days filtered_data['period'] = (filtered_data['diff'] > 1).cumsum() # 找出连续时间段，并计算起始时间和结束时间 result = filtered_data.groupby(['id', 'period']).agg(start_date=('date', 'min'), end_date=('date', 'max')) result = result[result['end_date'] - result['start_date'] > pd.Timedelta(days=7)].reset_index(drop=True) # 根据id排序输出结果 result = result.sort_values(by=['id']) print(result) ``` 输出结果将会按照企业id进行排序。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值