Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by erocs
, 1 year ago
onsider 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.
via Stack Overflow by Felipe
, 1 year ago
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.
via talend.com by Unknown author, 1 year ago
via Stack Overflow by danny
, 2 years ago
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.
via Stack Overflow by milind_db
, 2 years ago
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.
via Stack Overflow by dah
, 2 years ago
expiring and/or testi ng connection validity before use in your application, increasing the server con figured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 36,794,377 milliseconds ago.  The last packet sent successfully to the server was 36,794,377 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should c
onsider 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: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:404)	at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:983)	at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3644)	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2452)	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617)	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2550)	at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)	at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1962)	at vg.civcraft.mc.bettershards.database.DatabaseManager.isPlayerLocked(DatabaseManager.java:490)	at vg.civcraft.mc.bettershards.database.DatabaseManager$4.call(DatabaseManager.java:739)	at vg.civcraft.mc.bettershards.database.DatabaseManager$4.call(DatabaseManager.java:732)