com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 14,380,298 milliseconds ago. The last packet sent successfully to the server was 14,380,634 milliseconds ago.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    via Google Groups by Ghenadie DUMITRU

    There is a known issue between TestNG 6.4 and IDEA, the next EAP will fix this but in the meantime, use the previous version.

  2. ,

    not english

Solutions on the web

via Stack Overflow by D.Madu
, 1 year ago
Communications link failure The last packet successfully received from the server was 14,380,298 milliseconds ago. The last packet sent successfully to the server was 14,380,634 milliseconds ago.
via Stack Overflow by D.Madu
, 1 year ago
Communications link failure The last packet successfully received from the server was 14,391,063 milliseconds ago. The last packet sent successfully to the server was 14,391,344 milliseconds ago.
via Stack Overflow by Caffeine Coma
, 2 years ago
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
via GitHub by VincenzoFerme
, 1 year ago
The last packet successfully received from the server was 539,758,498 milliseconds ago. The last packet sent successfully to the server was 539,758,498 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failureThe last packet successfully received from the server was 14,380,298 milliseconds ago.  The last packet sent successfully to the server was 14,380,634 milliseconds ago.	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)	at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)	at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:989)	at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3743)	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2506)	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2677)	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2545)	at com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:4842)	at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)	at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)	at CreatePO.getItemFromDB(CreatePO.java:84)	at CreatePO.run(CreatePO.java:53)	at java.util.TimerThread.mainLoop(Timer.java:555)	at java.util.TimerThread.run(Timer.java:505)Caused by: java.net.SocketException: Connection reset by peer: socket write error	at java.net.SocketOutputStream.socketWrite0(Native Method)	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)	at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3725)	... 10 more