com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
No operations allowed after connection closed.
at
sun.reflect.GeneratedConstructorAccessor3.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at
com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1015)
at
com.mysql.jdbc.SQLError.createSQLException(SQLError.java:989)
at
com.mysql.jdbc.SQLError.createSQLException(SQLError.java:975)
at
com.mysql.jdbc.SQLError.createSQLException(SQLError.java:920)
at
com.mysql.jdbc.ConnectionImpl.throwConnectionClosedException(ConnectionImpl.java:1304)
at
com.mysql.jdbc.ConnectionImpl.checkClosed(ConnectionImpl.java:1296)
at
com.mysql.jdbc.ConnectionImpl.createStatement(ConnectionImpl.java:2676)
at
com.mysql.jdbc.ConnectionImpl.createStatement(ConnectionImpl.java:2658)
at db.Dao.insertAll(Dao.java:50)
at
file.unzip.FileReader.readFileWriteDb(FileReader.java:217)
at main.GetData.run(GetData.java:49)
at main.GetData.main(GetData.java:67)
Caused by:
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
packet successfully received from the server was 50,332,352
milliseconds ago. The last packet sent
successfully to the server was 50,332,345 milliseconds ago. is
longer than the server configured value of 'wait_timeout'. You
should consider either expiring and/or testing connection validity
before use in your application, increasing the server configured
values for client timeouts, or using the Connector/J connection
property 'autoReconnect=true' to avoid this problem.
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at
com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1121)
at
com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3673)
at
com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3562)
at
com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4113)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2570)
at
com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2731)
at
com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2812)
at
com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1811)
at
com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1725)
at db.Dao.insertAll(Dao.java:51)
... 3 more
Caused by: java.net.SocketException: Connection reset
at
java.net.SocketInputStream.read(SocketInputStream.java:168)
at
com.mysql.jdbc.util.ReadAheadInputStream.fill(ReadAheadInputStream.java:114)
at
com.mysql.jdbc.util.ReadAheadInputStream.readFromUnderlyingStreamIfNecessary(ReadAheadInputStream.java:161)
at
com.mysql.jdbc.util.ReadAheadInputStream.read(ReadAheadInputStream.java:189)
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:3116)
at
com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3573)
... 11 more
我的连接是一直活动的不该出这个问题. 然后我计算了一下最后一次接受信息的时间. 发现是14小时前.
就是昨天刚下班时候.
!!! 然后我去找电源选项 ,果然,那个dell的什么计划 半小时后就休眠了
气人啊
本文记录了一次MySQL连接异常的问题排查过程。主要问题是由于服务器连接超时导致的MySQLNonTransientConnectionException异常,通过调整服务器配置及客户端设置成功解决了问题。
825

被折叠的 条评论
为什么被折叠?



