com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 619,082,686 milliseconds ago. The last packet sent successfully to the server was 619,082,686 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.

Terracotta | abhutra | 5 years ago
  1. 0

    Re:Quartz failure in notifyJobStoreJobComplete method

    Terracotta | 5 years ago | abhutra
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 619,082,686 milliseconds ago. The last packet sent successfully to the server was 619,082,686 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

    Java scheduled thread kills database

    Stack Overflow | 4 years ago | Ali
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 86,892 milliseconds ago. The last packet sent successfully to the server was 27,333 milliseconds ago.
  3. 0

    Exception during keep alive check

    GitHub | 3 years ago | virtyvoid
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 746,568 milliseconds ago. The last packet sent successfully to the server was 2 milliseconds ago.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Talend - MySQL broken pipe error

    Stack Overflow | 3 years ago | Thomas Grady CBIP
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 344,265,715 milliseconds ago. The last packet sent successfully to the server was 344,265,792 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.
  6. 0

    help me avoid connection timeout with JPA, Hibernate & MySQL

    Stack Overflow | 6 years ago | Caffeine Coma
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 41,936,868 milliseconds ago. The last packet \ sent successfully to the server was 41,936,868 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expirin\ g and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connec\ tion property 'autoReconnect=true' to avoid this problem.

  1. mortalman7 3 times, last 5 months ago
  2. linxiaolong 2 times, last 4 weeks ago
  3. fima 28 times, last 2 months ago
  4. kuldeep 2 times, last 2 months ago
  5. mauritius 2 times, last 2 months ago
7 more registered users
5 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. com.mysql.jdbc.exceptions.jdbc4.CommunicationsException

    The last packet successfully received from the server was 619,082,686 milliseconds ago. The last packet sent successfully to the server was 619,082,686 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 sun.reflect.NativeConstructorAccessorImpl.newInstance0()
  2. Java RT
    Constructor.newInstance
    1. sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    2. sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    3. sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    4. java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    4 frames
  3. MySQL jdbc
    ConnectionImpl.setAutoCommit
    1. com.mysql.jdbc.Util.handleNewInstance(Util.java:407)
    2. com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116)
    3. com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3358)
    4. com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1970)
    5. com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2150)
    6. com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2620)
    7. com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5022)
    7 frames
  4. c3p0:JDBC DataSources/Resource Pools
    NewProxyConnection.setAutoCommit
    1. com.mchange.v2.c3p0.impl.NewProxyConnection.setAutoCommit(NewProxyConnection.java:881)
    1 frame
  5. quartz
    AttributeRestoringConnectionInvocationHandler.invoke
    1. org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.setAutoCommit(AttributeRestoringConnectionInvocationHandler.java:91)
    2. org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.invoke(AttributeRestoringConnectionInvocationHandler.java:65)
    2 frames
  6. Unknown
    $Proxy29.setAutoCommit
    1. $Proxy29.setAutoCommit(Unknown Source)
    1 frame
  7. quartz
    JobStoreSupport.executeInNonManagedTXLock
    1. org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:747)
    2. org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:69)
    3. org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3721)
    4. org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3693)
    4 frames