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)

Oracle Community | 392 Guest | 8 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    JMS connection

    Oracle Community | 8 years ago | 392 Guest
    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)
  2. 0

    Communications Exception after wait_timeout expires in MySQL 5

    Oracle Community | 8 years ago | loren_
    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)

    Root Cause Analysis

    1. 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()
    2. oracle.toplink.essentials
      DatabaseException.sqlException
      1. oracle.toplink.essentials.exceptions.DatabaseException.sqlException(DatabaseException.java:319)
      1 frame