Details

    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.
    • Operating System/s:
      Windows XP

      Description

      3.1.0 rc1 build 811

      when 'use batch update for inserts' is enabled in table output with a postgres connection the running transformation
      stops (see stacktrace below)
      The number of records that can be inserted depends to the setting of commit size.
      However, one of the column is of type date. When i explicit do a cast of this date to a char type,
      then everthings works fine.

      Prepared statement : INSERT INTO extractie.ext_woz_objectperceel (BELOBJNR, KADID, DDEINDE, OPPOBJECT, OPPGEBOBJECT) VALUES ( ?, ?, ?, ?, ?)
      Unexpected error :
      java.lang.IllegalArgumentException: Can't change resolved type for param: 3 from 1184 to 1114
      at org.postgresql.core.v3.SimpleParameterList.setResolvedType(SimpleParameterList.java:196)
      at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1201)
      at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
      at org.postgresql.jdbc2.AbstractJdbc2Connection.executeTransactionCommand(AbstractJdbc2Connection.java:653)
      at org.postgresql.jdbc2.AbstractJdbc2Connection.rollback(AbstractJdbc2Connection.java:690)
      at org.pentaho.di.core.database.Database.rollback(Database.java:656)
      at org.pentaho.di.core.database.Database.rollback(Database.java:641)
      at org.pentaho.di.trans.steps.tableoutput.TableOutput.writeToTable(TableOutput.java:375)
      at org.pentaho.di.trans.steps.tableoutput.TableOutput.processRow(TableOutput.java:78)
      at org.pentaho.di.trans.step.BaseStep.runStepThread(BaseStep.java:2655)
      at org.pentaho.di.trans.steps.tableoutput.TableOutput.run(TableOutput.java:630)
      Unexpected error committing the database connection.
      org.pentaho.di.core.exception.KettleDatabaseException:
      Error comitting connection
      An I/O error occured while sending to the backend.

      at org.pentaho.di.core.database.Database.commit(Database.java:635)
      at org.pentaho.di.core.database.Database.commit(Database.java:605)
      at org.pentaho.di.core.database.Database.emptyAndCommit(Database.java:1377)
      at org.pentaho.di.trans.steps.tableoutput.TableOutput.dispose(TableOutput.java:563)
      at org.pentaho.di.trans.step.BaseStep.runStepThread(BaseStep.java:2674)
      at org.pentaho.di.trans.steps.tableoutput.TableOutput.run(TableOutput.java:630)
      Caused by: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend.
      at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217)
      at org.postgresql.jdbc2.AbstractJdbc2Connection.executeTransactionCommand(AbstractJdbc2Connection.java:653)
      at org.postgresql.jdbc2.AbstractJdbc2Connection.commit(AbstractJdbc2Connection.java:673)
      at org.pentaho.di.core.database.Database.commit(Database.java:625)
      ... 5 more
      Caused by: java.io.IOException: Unexpected packet type: 0
      at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1438)
      at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
      ... 8 more
      org.pentaho.di.core.exception.KettleDatabaseException:
      Error comitting connection
      An I/O error occured while sending to the backend.

      at org.pentaho.di.core.database.Database.commit(Database.java:635)
      at org.pentaho.di.core.database.Database.commit(Database.java:605)
      at org.pentaho.di.core.database.Database.emptyAndCommit(Database.java:1377)
      at org.pentaho.di.trans.steps.tableoutput.TableOutput.dispose(TableOutput.java:563)
      at org.pentaho.di.trans.step.BaseStep.runStepThread(BaseStep.java:2674)
      at org.pentaho.di.trans.steps.tableoutput.TableOutput.run(TableOutput.java:630)
      Caused by: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend.
      at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217)
      at org.postgresql.jdbc2.AbstractJdbc2Connection.executeTransactionCommand(AbstractJdbc2Connection.java:653)
      at org.postgresql.jdbc2.AbstractJdbc2Connection.commit(AbstractJdbc2Connection.java:673)
      at org.pentaho.di.core.database.Database.commit(Database.java:625)
      ... 5 more
      Caused by: java.io.IOException: Unexpected packet type: 0
      at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1438)
      at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
      ... 8 more
      Unexpected error rolling back the database connection.
      org.pentaho.di.core.exception.KettleDatabaseException:
      Error performing rollback on connection
      An I/O error occured while sending to the backend.

      at org.pentaho.di.core.database.Database.rollback(Database.java:667)
      at org.pentaho.di.core.database.Database.rollback(Database.java:641)
      at org.pentaho.di.trans.steps.tableoutput.TableOutput.dispose(TableOutput.java:613)
      at org.pentaho.di.trans.step.BaseStep.runStepThread(BaseStep.java:2674)
      at org.pentaho.di.trans.steps.tableoutput.TableOutput.run(TableOutput.java:630)
      Caused by: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend.
      at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217)
      at org.postgresql.jdbc2.AbstractJdbc2Connection.executeTransactionCommand(AbstractJdbc2Connection.java:653)
      at org.postgresql.jdbc2.AbstractJdbc2Connection.rollback(AbstractJdbc2Connection.java:690)
      at org.pentaho.di.core.database.Database.rollback(Database.java:656)
      ... 4 more
      Caused by: java.io.IOException: Stream closed
      at sun.nio.cs.StreamEncoder.ensureOpen(Unknown Source)
      at sun.nio.cs.StreamEncoder.flush(Unknown Source)
      at java.io.OutputStreamWriter.flush(Unknown Source)
      at org.postgresql.core.PGStream.flush(PGStream.java:507)
      at org.postgresql.core.v3.QueryExecutorImpl.sendSync(QueryExecutorImpl.java:675)
      at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:190)
      ... 7 more

        Issue Links

          Activity

          Hide
          jbleuel Jens Bleuel added a comment -

          I believe this is a JDBC driver issue, see http://archives.postgresql.org/pgsql-jdbc/2007-09/msg00084.php

          "Interestingly, if I drop back to the older driver I was using with the 8.1.8 back-end (postgresql-8.1-408.jdbc3.jar), but run it against the 8.2.4 back-end, the import completes without error! "

          Show
          jbleuel Jens Bleuel added a comment - I believe this is a JDBC driver issue, see http://archives.postgresql.org/pgsql-jdbc/2007-09/msg00084.php "Interestingly, if I drop back to the older driver I was using with the 8.1.8 back-end (postgresql-8.1-408.jdbc3.jar), but run it against the 8.2.4 back-end, the import completes without error! "
          Hide
          mcasters Matt Casters added a comment -

          This indeed looks like a PostgreSQL error, but it remains to be seen if it's located on the server side or the client side (JDBC).
          On a side note I would like you to stop using 3.1.0 RC1.

          Show
          mcasters Matt Casters added a comment - This indeed looks like a PostgreSQL error, but it remains to be seen if it's located on the server side or the client side (JDBC). On a side note I would like you to stop using 3.1.0 RC1.
          Hide
          rutgerdow Rutger Deterd Oude Weme added a comment -

          postgres driver 8.2-506 I'm using is the problem.
          I replaced it by version 8.3-603 and the transformation is running ok.
          (with 3.1.0 build 826)

          Show
          rutgerdow Rutger Deterd Oude Weme added a comment - postgres driver 8.2-506 I'm using is the problem. I replaced it by version 8.3-603 and the transformation is running ok. (with 3.1.0 build 826)
          Hide
          jbleuel Jens Bleuel added a comment -

          Other user with 3.0.4 reported success with using 8.3-603. I guess it is also related to 3.1 GA but did not verify.

          Rev. 9205 & 9206 replaced the driver in trunk and 3.1.1 with postgresql-8.3-603.jdbc4.jar (following the PostgreSQL recommendation and be save with 1.6 JVM: "If you are using the 1.6 JVM, then you should use the JDBC4 version.")

          Circumvention is to download the driver here: http://jdbc.postgresql.org/download.html
          and replace it in libext/JDBC (delete the old 8.2 one).

          Show
          jbleuel Jens Bleuel added a comment - Other user with 3.0.4 reported success with using 8.3-603. I guess it is also related to 3.1 GA but did not verify. Rev. 9205 & 9206 replaced the driver in trunk and 3.1.1 with postgresql-8.3-603.jdbc4.jar (following the PostgreSQL recommendation and be save with 1.6 JVM: "If you are using the 1.6 JVM, then you should use the JDBC4 version.") Circumvention is to download the driver here: http://jdbc.postgresql.org/download.html and replace it in libext/JDBC (delete the old 8.2 one).
          Hide
          jbleuel Jens Bleuel added a comment -

          Just for reference: User also got this error message with a high commit size.
          Java.io.IOException : stream closed

          With a low commit size he got the error above.

          All has gone with the new driver

          Show
          jbleuel Jens Bleuel added a comment - Just for reference: User also got this error message with a high commit size. Java.io.IOException : stream closed With a low commit size he got the error above. All has gone with the new driver
          Hide
          happyarts Markus Kaemmerer added a comment -

          Just for information: we use the new postgresql jdbc driver sind months and it is working without problems.

          Show
          happyarts Markus Kaemmerer added a comment - Just for information: we use the new postgresql jdbc driver sind months and it is working without problems.
          Hide
          mcasters Matt Casters added a comment -

          Jens, the JDBC driver you checked in breaks the project as it doesn't compile on 1.5.
          Can you please un-install your 1.6 JRE/JDK as well?
          Thanks.

          Show
          mcasters Matt Casters added a comment - Jens, the JDBC driver you checked in breaks the project as it doesn't compile on 1.5. Can you please un-install your 1.6 JRE/JDK as well? Thanks.
          Hide
          jbleuel Jens Bleuel added a comment -

          Exchanged with the JDBC3 version: postgresql-8.3-603.jdbc3.jar
          in Rev. 9225 & 9226

          Show
          jbleuel Jens Bleuel added a comment - Exchanged with the JDBC3 version: postgresql-8.3-603.jdbc3.jar in Rev. 9225 & 9226
          Hide
          jbleuel Jens Bleuel added a comment -

          It's building again

          Show
          jbleuel Jens Bleuel added a comment - It's building again

            People

            • Assignee:
              jbleuel Jens Bleuel
              Reporter:
              rutgerdow Rutger Deterd Oude Weme
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: