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 Terracotta by abhutra, 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 Stack Overflow by Caffeine Coma
, 2 years ago
consider either expirin\ g and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connec\ tion 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.
via talend.com by Unknown author, 2 years ago
via Stack Overflow by hypercube
, 9 months ago
Communications link failure Last packet sent to the server was 0 ms ago.
via GitHub by Craft4
, 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.
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 619,082,686 
milliseconds ago.  The last packet sent successfully to the server was
619,082,686 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:407)	at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116)	at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3358)	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1970)	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2150)	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2620)	at com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5022)	at com.mchange.v2.c3p0.impl.NewProxyConnection.setAutoCommit(NewProxyConnection.java:881)	at org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.setAutoCommit(AttributeRestoringConnectionInvocationHandler.java:91)	at org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.invoke(AttributeRestoringConnectionInvocationHandler.java:65)	at $Proxy29.setAutoCommit(Unknown Source)	at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:747)	at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:69)	at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3721)	at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3693)