org.pentaho.di.core.exception.KettleDatabaseException: Couldn't get row from result set Communications link failure The last packet successfully received from the server was 15,483 milliseconds ago. The last packet sent successfully to the server was 1 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

Solutions on the web

via pentaho.com by Unknown author, 9 months ago
Couldn't get row from result set Communications link failure The last packet successfully received from the server was 15,483 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago.
via Database Administrators by Codek
, 1 year ago
Couldn't get row from result set Communications link failure The last packet successfully received from the server was 142 milliseconds ago. The last packet sent successfully to the server was 14,468,141 milliseconds ago.
via Pentaho BI Platform Tracking by John Gallagher, 5 months ago
Couldn't get row from result set Unable to get value 'Integer(38)' from database resultset, index 24 Numeric Overflow
via pentaho.com by Unknown author, 2 years ago
Couldn't get row from result set Unable to get value 'String(100)<binary-string>' from database resultset, index 12 [Microsoft][ODBC Driver Manager] Invalid string or buffer length
via Stack Overflow by mounaim
, 7 months ago
2017/04/04 11:00:56 - read from [DEMANDE].0 - Couldn't get row from result set 2017/04/04 11:00:56 - read from [DEMANDE].0 - 2017/04/04 11:00:56 - read from [DEMANDE].0 - Unable to get value 'Integer(38)' from database resultset, index 3 2017/04/04
via pentaho.com by Unknown author, 1 year ago
- Couldn't get row from result set - IO Error: Socket read timed out
org.pentaho.di.core.exception.KettleDatabaseException: Couldn't get row from result set Communications link failure The last packet successfully received from the server was 15,483 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago.
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:2540)
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2990)
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2979)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3520)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:935)
at com.mysql.jdbc.MysqlIO.nextRow(MysqlIO.java:1433)
at com.mysql.jdbc.MysqlIO.fetchRowsViaCursor(MysqlIO.java:4714)
at com.mysql.jdbc.RowDataCursor.fetchMoreRows(RowDataCursor.java:412)
at com.mysql.jdbc.RowDataCursor.hasNext(RowDataCursor.java:318)
at com.mysql.jdbc.RowDataCursor.next(RowDataCursor.java:358)
at com.mysql.jdbc.ResultSetImpl.next(ResultSetImpl.java:7165)
at org.pentaho.di.core.database.Database.getRow(Database.java:2784)
at org.pentaho.di.core.database.Database.getRow(Database.java:2768)
at org.pentaho.di.trans.steps.tableinput.TableInput.processRow(TableInput.java:143)
at org.pentaho.di.trans.step.RunThread.run(RunThread.java:40)
at java.lang.Thread.run(Thread.java:636)

Users with the same issue

10 times, 4 months ago
Once, 5 months ago
4 times, 5 months ago
2 times, 5 months ago
Once, 9 months ago
19 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.