com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the serv er was39292 seconds ago.The last packet sent successfully to the server was 39292 seconds ago, which is longer than the server configured value of 'w ait_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.

activiti.org | 7 months ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    MySQL Exception | Activiti Forums

    activiti.org | 7 months ago
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the serv er was39292 seconds ago.The last packet sent successfully to the server was 39292 seconds ago, which is longer than the server configured value of 'w ait_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

    high availability - JBoss don't fail over MySQL slave using datasource - Database Administrators Stack Exchange

    stackexchange.com | 1 year ago
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 1 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.

    Root Cause Analysis

    1. com.mysql.jdbc.exceptions.jdbc4.CommunicationsException

      The last packet successfully received from the serv er was39292 seconds ago.The last packet sent successfully to the server was 39292 seconds ago, which is longer than the server configured value of 'w ait_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.ibatis.transaction.jdbc.JdbcTransaction.setDesiredAutoCommit()
    2. MyBatis
      DefaultSqlSession.selectList
      1. org.apache.ibatis.transaction.jdbc.JdbcTransaction.setDesiredAutoCommit(JdbcTransaction.java:102)
      2. org.apache.ibatis.transaction.jdbc.JdbcTransaction.openConnection(JdbcTransaction.java:135)
      3. org.apache.ibatis.transaction.jdbc.JdbcTransaction.getConnection(JdbcTransaction.java:58)
      4. org.apache.ibatis.executor.BaseExecutor.getConnection(BaseExecutor.java:279)
      5. org.apache.ibatis.executor.SimpleExecutor.prepareStatement(SimpleExecutor.java:69)
      6. org.apache.ibatis.executor.SimpleExecutor.doQuery(SimpleExecutor.java:56)
      7. org.apache.ibatis.executor.BaseExecutor.queryFromDatabase(BaseExecutor.java:267)
      8. org.apache.ibatis.executor.BaseExecutor.query(BaseExecutor.java:141)
      9. org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:105)
      10. org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:81)
      11. org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:101)
      11 frames