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 github.com by Unknown author

    Upgrade your docker-selenium

  2. ,
    via github.com by Unknown author

    Probably there is a bug in TestNG Eclipse plugin (6.8.6.20130607_0745), try an other version (e.g. 6.8.0.20121120_1820)

Solutions on the web

via pentaho.com by Unknown author, 2 years ago
There was an error calculating the change data capture date range, it probably involved log table trans_log. Couldn't execute SQL: LOCK TABLE audit.trans_log IN ACCESS EXCLUSIVE MODE An I/O error occured while sending to the backend.
via pentaho.com by Unknown author, 1 year ago
There was an error calculating the change data capture date range, it probably involved log table trans_log. Couldn't execute SQL: LOCK TABLE audit.trans_log IN ACCESS EXCLUSIVE MODE An I/O error occured while sending to the backend.
via GitHub by HiromuHota
, 7 months ago
2017/08/23 17:43:36 - Spoon - There was an error calculating the change data capture date range, it probably involved log table null. 2017/08/23 17:43:36 - Spoon - 2017/08/23 17:43:36 - Spoon - No log table has been defined for the transformation. 2017/08/23 17:43:36 - Spoon - 2017/08/23 17:43:36 - Spoon -
via Pentaho BI Platform Tracking by Carlos Lopez, 5 months ago
2017/10/25 17:31:02 - Generate DIM_DATE - There was an error calculating the change data capture date range, it probably involved log table null. 2017/10/25 17:31:02 - Generate DIM_DATE - 2017/10/25 17:31:02 - Generate DIM_DATE - No log table has been defined for the transformation. 2017/10/25 17:31:02 - Generate DIM_DATE - 2017/10/25 17:31:02 - Generate DIM_DATE -
via Stack Overflow by Elias Gezahegn
, 3 months ago
There was an error calculating the change data capture date range, it probably involved log table trans_logs. Error occurred while trying to connect to the database Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
java.net.SocketException: Connection reset by peer: socket write error	at java.net.SocketOutputStream.socketWrite0(Native Method)	at java.net.SocketOutputStream.socketWrite(Unknown Source)	at java.net.SocketOutputStream.write(Unknown Source)	at java.io.BufferedOutputStream.flushBuffer(Unknown Source)	at java.io.BufferedOutputStream.flush(Unknown Source)	at org.postgresql.core.PGStream.flush(PGStream.java:521)	at org.postgresql.core.v3.QueryExecutorImpl.sendSync(QueryExecutorImpl.java:1141)	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:254)	at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:510)	at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:372)	at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:364)	at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:261)	at org.pentaho.di.core.database.Database.execStatement(Database.java:1406)	at org.pentaho.di.core.database.Database.execStatements(Database.java:1538)	at org.pentaho.di.core.database.Database.execStatements(Database.java:1458)	at org.pentaho.di.core.database.Database.lockTables(Database.java:3859)	at org.pentaho.di.core.database.BaseDatabaseMeta.getNextBatchIdUsingLockTables(BaseDatabaseMeta.java:1966)	at org.pentaho.di.core.database.BaseDatabaseMeta.getNextBatchId(BaseDatabaseMeta.java:2006)	at org.pentaho.di.core.database.DatabaseMeta.getNextBatchId(DatabaseMeta.java:2620)	at org.pentaho.di.trans.Trans.calculateBatchIdAndDateRange(Trans.java:1896)	at org.pentaho.di.trans.Trans.prepareExecution(Trans.java:904)	at org.pentaho.di.ui.spoon.trans.TransGraph$26.run(TransGraph.java:3885)	at java.lang.Thread.run(Unknown Source)