mysql5.7转移_mysql从5.7.17迁移到5.7.22业务报错

本帖最后由 mark_huang 于 2018-5-22 16:45 编辑

mysql从5.7.17迁移到5.7.22后,业务半个月报错2次(报错时间毫无规律) 以下是业务报错日志,truncate表后重启执行程序业务恢复正常。 原库和新库的 wait_timeout都是8个小时

2018-05-20 06:30:30.020 [schedulerFactoryBean_Worker-3] INFO  org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml]

2018-05-20 06:30:30.127 [schedulerFactoryBean_Worker-3] INFO  org.springframework.jdbc.support.SQLErrorCodesFactory - SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase, Hana]

2018-05-20 06:30:30.178 [schedulerFactoryBean_Worker-3] INFO  com.mark.stat.sync.service.impl.ReportTripCoServiceImpl - [LOGGERID: 1526769000010-541] 表重算捕获异常===org.springframework.dao.RecoverableDataAccessException:

### Error updating database.  Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

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

### The error may involve defaultParameterMap

### The error occurred while setting parameters

### SQL: delete from  mark_report

### Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

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

; SQL []; Communications link failure

The last packet successfully received from the server was 624 milliseconds ago.  The last packet sent successfully to the server was 624 milliseconds ago.; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

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

2018-05-20 06:30:30.179 [schedulerFactoryBean_Worker-3] INFO  com.mark.stat.sync.service.impl.JobExecuteServiceImpl - [LOGGERID: 1526769000010-541] 重算任务释放锁

2018-05-20 06:40:00.009 [schedulerFactoryBean_Worker-4] INFO  com.mark.stat.sync.service.impl.JobExecuteServiceImpl - [LOGGERID: 1526769600009-702] 重算任务开始获取锁

2018-05-20 06:40:00.009 [schedulerFactoryBean_Worker-4] INFO  com.mark.stat.sync.service.impl.JobExecuteServiceImpl - [LOGGERID: 1526769600009-702] 重算任务获取锁成功

2018-05-20 06:40:00.019 [schedulerFactoryBean_Worker-4] INFO  com.mark.stat.sync.service.impl.JobExecuteServiceImpl - [LOGGERID: 1526769600009-702] 表重算任务开始-------- start --------

2018-05-20 06:40:00.145 [schedulerFactoryBean_Worker-4] INFO  com.mark.stat.sync.service.impl.ReportTripCoServiceImpl - [LOGGERID: 1526769600009-702] [timecost(ms): 136] 查询需要重算的记录

2018-05-20 06:40:20.682 [schedulerFactoryBean_Worker-4] INFO  com.mark.stat.sync.service.impl.ReportTripCoServiceImpl - [LOGGERID: 1526769600009-702] 表重算捕获异常===org.springframework.dao.RecoverableDataAccessException:

### Error updating database.  Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

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

### The error may involve defaultParameterMap

### The error occurred while setting parameters

### SQL: delete from  mark_report

### Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

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

; SQL []; Communications link failure

The last packet successfully received from the server was 136 milliseconds ago.  The last packet sent successfully to the server was 136 milliseconds ago.; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值