JEEBBS论坛 » BUG反馈 » com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

主题 : com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure |
级别: 商业授权用户
![]() |
2# 发表于:2015-12-25 21:55:24 IP:116.191.*.*
The last packet successfully received from the server was 110,622 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago.
at sun.reflect.GeneratedConstructorAccessor57.newInstance(Unknown Source) ~[na:na] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) ~[na:1.6.0_43] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) ~[na:1.6.0_43] at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1129) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3720) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3609) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4160) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2617) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2778) ~[mysql-connector-java-5.1.28.jar:na] |
||
---|---|---|---|
级别: 商业授权用户
![]() |
3# 发表于:2015-12-25 21:55:45 IP:116.191.*.*
21:30:23.362 ERROR org.hibernate.transaction.JDBCTransaction - JDBC begin failed
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 110,622 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago. at sun.reflect.GeneratedConstructorAccessor57.newInstance(Unknown Source) ~[na:na] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) ~[na:1.6.0_43] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) ~[na:1.6.0_43] at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1129) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3720) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3609) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4160) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2617) ~[mysql-connector-java-5.1.28.jar:na] at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2778) ~[mysql-connector-java-5.1.28.jar:na] |
||
---|---|---|---|
级别: 版主
![]() |
6# 发表于:2015-12-26 15:57:17 IP:106.199.*.*
修改方法:MySQL通过my.ini 在
# The TCP/IP Port the MySQL Server will listen on port=3306下面添加 # this is myown dinifition for mysql connection timeout wait_timeout=31536000 interactive_timeout=31536000 试下这个方法 |
||
---|---|---|---|
级别: 商业授权用户
![]() |
7# 发表于:2015-12-26 16:46:56 IP:220.19.*.*
这个方法我试过,还是不行,同样的数据库,另外一个程序就不出现此问题,这个jeecmsv7为何出现此问题,有人遇到吗???
|
||
---|---|---|---|
级别: 商业授权用户
![]() |
8# 发表于:2015-12-26 16:48:38 IP:220.19.*.*
wait_timeout 过大有弊端,其体现就是MySQL里大量的SLEEP进程无法及时释放,拖累系统性能,不过也不能把这个指设置的过小,否则你可能会遭遇到“MySQL has gone away”之类的问题,通常来说,把wait_timeout设置为10是个不错的选择,
|
||
---|---|---|---|