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 | loren_ | 8 years ago
  1. 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)
  2. 0

    JMS connection

    Oracle Community | 7 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)
  3. 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.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    JMS connection

    Oracle Community | 7 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.
  6. 0

    Installation - Kaldin Q&A

    kaldin.com | 8 months ago
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was66818 milliseconds ago.The last packet sent successfully to the server was 66818 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.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    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