本帖最后由 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

總結

以上是生活随笔為你收集整理的mysql5.7转移_mysql从5.7.17迁移到5.7.22业务报错的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。