com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 36,794,377 milliseconds ago. The last packet sent successfully to the server was 36,794,377 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should c onsider 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.

GitHub | erocs | 4 months ago
  1. 0

    CommunicationsException DatabaseManager.isPlayerLocked

    GitHub | 4 months ago | erocs
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 36,794,377 milliseconds ago. The last packet sent successfully to the server was 36,794,377 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should c onsider 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

    Is there any free GPS Simulator supported by traccar?

    GitHub | 3 years ago | mikeandersun
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure||The last packet successfully received from the server was 37,854,262 milliseconds ago. The last packet sent successfully to the server was 2 milliseconds ago.
  3. 0

    Hibernate first login failed

    Stack Overflow | 2 years ago | Yair Cohen
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure||The last packet successfully received from the server was 83,961 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Hibernate / MySQL connection timeouts -- Trying to deal with thread-pooled executors not releasing Hibernate connections to C3P0 after exit

    Stack Overflow | 4 years ago | Jayadev Jayaraman
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 1,326,037 milliseconds ago. The last packet sent successfully to the server was 660,100 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

    glassfish - connection with mysql crashes

    Stack Overflow | 4 years ago | greenskin
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure</p> <p>The last packet successfully received from the server was 30 886 849 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.</p> <pre><code>at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

  1. fima 28 times, last 2 months ago
  2. kuldeep 2 times, last 3 months ago
  3. mortalman7 1 times, last 5 months ago
  4. linxiaolong 2 times, last 1 month ago
  5. mauritius 2 times, last 3 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 36,794,377 milliseconds ago. The last packet sent successfully to the server was 36,794,377 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should c onsider 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)[?:1.8.0_91]
    2. sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)[?:1.8.0_91]
    3. sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[?:1.8.0_91]
    4. java.lang.reflect.Constructor.newInstance(Constructor.java:423)[?:1.8.0_91]
    4 frames
  3. MySQL jdbc
    PreparedStatement.executeQuery
    1. com.mysql.jdbc.Util.handleNewInstance(Util.java:404)[spigot.jar:git-Spigot-e0e1771-5e5cf84]
    2. com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:983)[spigot.jar:git-Spigot-e0e1771-5e5cf84]
    3. com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3644)[spigot.jar:git-Spigot-e0e1771-5e5cf84]
    4. com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2452)[spigot.jar:git-Spigot-e0e1771-5e5cf84]
    5. com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617)[spigot.jar:git-Spigot-e0e1771-5e5cf84]
    6. com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2550)[spigot.jar:git-Spigot-e0e1771-5e5cf84]
    7. com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)[spigot.jar:git-Spigot-e0e1771-5e5cf84]
    8. com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1962)[spigot.jar:git-Spigot-e0e1771-5e5cf84]
    8 frames
  4. vg.civcraft.mc
    DatabaseManager$4.call
    1. vg.civcraft.mc.bettershards.database.DatabaseManager.isPlayerLocked(DatabaseManager.java:490)[BetterShards.jar:?]
    2. vg.civcraft.mc.bettershards.database.DatabaseManager$4.call(DatabaseManager.java:739)[BetterShards.jar:?]
    3. vg.civcraft.mc.bettershards.database.DatabaseManager$4.call(DatabaseManager.java:732)[BetterShards.jar:?]
    3 frames