org.apache.openjpa.persistence.PersistenceException: The last packet successfully received from the server was 187,404,662 milliseconds ago. The last packet sent successfully to the server was 187,404,662 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.

openjpa-users | David Beer | 4 years ago
  1. 0

    MySQL Timeout issue

    openjpa-users | 4 years ago | David Beer
    org.apache.openjpa.persistence.PersistenceException: The last packet successfully received from the server was 187,404,662 milliseconds ago. The last packet sent successfully to the server was 187,404,662 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.
  2. 0

    Oozie servers stop to work when restart mysql

    oozie-user | 2 years ago | Hill Liu
    org.apache.openjpa.persistence.PersistenceException: Communications link failure The last packet successfully received from the server was 14,288 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.
  3. 0

    Oozie servers stop to work when restart mysql

    oozie-user | 2 years ago | Hill Liu
    org.apache.openjpa.persistence.PersistenceException: Communications link failure The last packet successfully received from the server was 14,288 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    org.apache.openjpa.lib.jdbc.ReportingSQLException, MySQL, OpenJPA, Geronimo

    Stack Overflow | 5 years ago | AR3Y35
    org.apache.openjpa.persistence.PersistenceException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE = innodb' at line 1 {stmnt 1243851750 CREATE TABLE ADMIN_USER (admin_id BIGINT NOT NULL AUTO_INCREMENT, first_name VARCHAR(255), last_name VARCHAR(255), user_name VARCHAR(255), PRIMARY KEY (admin_id)) TYPE = innodb} [code=1064, state=42000]
  6. 0

    Concurrent access issue with JPA  for a Select query?

    Oracle Community | 4 years ago | java4ever
    org.apache.openjpa.persistence.PersistenceException: Multiple concurrent th reads attempted to access a single broker. By default brokers are not thread safe; if you require and/or intend a broker to be accessed by more than one thread, set the openjpa.Multithreaded property to true to override the default behavior.

    1 unregistered visitors
    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. org.apache.openjpa.persistence.PersistenceException

      The last packet successfully received from the server was 187,404,662 milliseconds ago. The last packet sent successfully to the server was 187,404,662 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 org.apache.openjpa.jdbc.sql.DBDictionary.narrow()
    2. OpenJPA Aggregate Jar
      DBDictionary.newStoreException
      1. org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4918)
      2. org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4878)
      2 frames