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 Oracle Community by loren_, 1 year ago
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. Error Code: 0 Call
via Oracle Community by 392 Guest, 1 year ago
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. Error Code: 0 Call
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was85533 milliseconds ago.The last packet sent successfully to the server was 85533 milliseconds ago, which 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. Error Code: 0 Call: SELECT AccountID, DateDeactivated, DateCreated, AcctMgr, RefContactID FROM Accounts WHERE (AccountID = ?) bind => [1000213] Query: ReadObjectQuery(com.myco.myapp.Account)	at oracle.toplink.essentials.exceptions.DatabaseException.sqlException(DatabaseException.java:319)