java.io.IOException: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 252 milliseconds ago. The last packet sent successfully to the server was 3,582,723 milliseconds ago.

GitHub | TheWildHorse | 8 months 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

    GitHub comment 868#239445250

    GitHub | 8 months ago | TheWildHorse
    java.io.IOException: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 252 milliseconds ago. The last packet sent successfully to the server was 3,582,723 milliseconds ago.
  2. 0

    Database connection drop error message in the console.

    GitHub | 4 years ago | cartman-2000
    com.griefcraft.scripting.ModuleException: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 62,656,333 milliseconds ago. The last packet sent successfully to the server was 62,656,333 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.
  3. 0

    Table Output step - Connection problem

    pentaho.com | 8 months ago
    org.pentaho.di.core.exception.KettleDatabaseException: Error comitting connection Unable to get database metadata from this database connection No operations allowed after connection closed.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    MySQL reconnect issue

    GitHub | 4 years ago | SelbieNL
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 46,012,347 milliseconds ago. The last packet sent successfully to the server was 46,012,348 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

    Strange things ;p

    GitHub | 4 years ago | freakyy85
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 39,695,385 milliseconds ago. The last packet sent successfully to the server was 39,695,385 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.

  1. mortalman7 1 times, last 4 months ago
  2. Hronom 3 times, last 4 months ago
  3. kuldeep 4 times, last 7 months ago
  4. esaar 1 times, last 9 months ago
  5. mauritius 2 times, last 1 year ago
17 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. java.net.SocketException

    Broken pipe

    at java.net.SocketOutputStream.socketWrite0()
  2. Java RT
    BufferedOutputStream.flush
    1. java.net.SocketOutputStream.socketWrite0(Native Method)[?:1.8.0_101]
    2. java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)[?:1.8.0_101]
    3. java.net.SocketOutputStream.write(SocketOutputStream.java:153)[?:1.8.0_101]
    4. java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)[?:1.8.0_101]
    5. java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)[?:1.8.0_101]
    5 frames
  3. MySQL jdbc
    ResultSetImpl.close
    1. com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3634)[mysql-connector-java-5.1.38.jar:5.1.38]
    2. com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2460)[mysql-connector-java-5.1.38.jar:5.1.38]
    3. com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2625)[mysql-connector-java-5.1.38.jar:5.1.38]
    4. com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2547)[mysql-connector-java-5.1.38.jar:5.1.38]
    5. com.mysql.jdbc.StatementImpl.executeSimpleNonQuery(StatementImpl.java:1454)[mysql-connector-java-5.1.38.jar:5.1.38]
    6. com.mysql.jdbc.RowDataDynamic.close(RowDataDynamic.java:178)[mysql-connector-java-5.1.38.jar:5.1.38]
    7. com.mysql.jdbc.ResultSetImpl.realClose(ResultSetImpl.java:6709)[mysql-connector-java-5.1.38.jar:5.1.38]
    8. com.mysql.jdbc.ResultSetImpl.close(ResultSetImpl.java:851)[mysql-connector-java-5.1.38.jar:5.1.38]
    8 frames
  4. org.xbib.elasticsearch
    StandardSource.execute
    1. org.xbib.elasticsearch.jdbc.strategy.standard.StandardSource.close(StandardSource.java:1130)[elasticsearch-jdbc-2.3.4.0.jar:?]
    2. org.xbib.elasticsearch.jdbc.strategy.standard.StandardSource.execute(StandardSource.java:701)[elasticsearch-jdbc-2.3.4.0.jar:?]
    2 frames