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
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

    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

    [OPENJPA-1197] NativeQueries fail with MySQL - ASF JIRA

    apache.org | 2 years ago
    org.apache.openjpa.persistence.PersistenceException: Unable to retrieve metadata for procedure.
  3. 0

    The transaction is no longer active - Transacti... | Oracle Community

    oracle.com | 2 years ago
    org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [OPENJPA-172] DSRA9250E: Operation setTransactionIsolation is not allowed during a global transaction for Shareable Connections. - ASF JIRA

    apache.org | 2 years ago
    org.apache.openjpa.persistence.PersistenceException: DSRA9250E: Operation setTransactionIsolation is not allowed during a global transaction for Shareable Connections.
  6. 0

    RE: OpenJPA opening excessive connections to SQLServer

    openjpa-users | 9 years ago | Patel Amit
    org.apache.openjpa.persistence.PersistenceException: The TCP/IP connection to the host has failed. java.net.BindException: Address already in use: connect

    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