Hitachi Vantara Pentaho Community Forums
Results 1 to 4 of 4

Thread: Access Violations Causing Kettle to Terminate

  1. #1
    Join Date
    Aug 2007
    Posts
    4

    Default Access Violations Causing Kettle to Terminate

    I am having a consistant problem running Kettle 2.5.1 (on Windows XP) and accessing a DB2 subsystem using a Neon ODBC driver. Kettle will start fetching data and will suddenly disappear. There are times where it will fetch the data for a while, and then disappear again. I looked in the log file and found the following:

    An unexpected exception has been detected in native code outside the VM.
    Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x7C901010
    Function=RtlEnterCriticalSection+0xB
    Library=C:\WINDOWS\system32\ntdll.dll
    Current Java thread:
    at sun.jdbc.odbc.JdbcOdbc.cancel(Native Method)
    at sun.jdbc.odbc.JdbcOdbc.SQLCancel(Unknown Source)
    at sun.jdbc.odbc.JdbcOdbcStatement.cancel(Unknown Source)
    at be.ibridge.kettle.core.database.Database.cancelStatement(Database.java:547)
    at be.ibridge.kettle.core.database.Database.cancelQuery(Database.java:532)
    at be.ibridge.kettle.trans.step.tableinput.TableInput.stopRunning(TableInput.java:238)
    at be.ibridge.kettle.trans.Trans.stopAll(Trans.java:933)
    at be.ibridge.kettle.trans.step.BaseStep.stopAll(BaseStep.java:1620)
    at be.ibridge.kettle.trans.step.BaseStep.getRow(BaseStep.java:1159)
    - locked <0x1318dd78> (a be.ibridge.kettle.trans.step.selectvalues.SelectValues)
    at be.ibridge.kettle.trans.step.selectvalues.SelectValues.processRow(SelectValues.java:299)
    at be.ibridge.kettle.trans.step.selectvalues.SelectValues.run(SelectValues.java:369)

    Any suggestions would be appreciated!

    Thanks.

  2. #2
    Join Date
    May 2006
    Posts
    4,882

    Default

    It's a Neon problem "An unexpected exception has been detected in native code outside the VM" probably... Try accessing DB2 via another way.

    Regards,
    Sven

  3. #3
    Join Date
    Nov 1999
    Posts
    9,729

    Default

    The cause is a programming error in the ODBC driver somewhere. I wish I could help you out here, but I don't think there's a lot we can do about it.

    Matt

  4. #4
    Join Date
    Aug 2007
    Posts
    4

    Default

    Thanks for the reply Matt and Sven. I am trying to get an updated driver from the vendor. The one perplexing aspect of this problem is that I don't have a problem with this same driver when using QTODBC. I can run the same query without incident, from the same machine, and not have it blow up.

    Regards.

    John

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.