Uploaded image for project: 'Pentaho Data Integration - Kettle'
  1. Pentaho Data Integration - Kettle
  2. PDI-14981

!Job.Exception.ErrorHandlingJobTransaction! error thrown when parent job is not db transactional, but child transformation is db transactional

    XMLWordPrintable

    Details

    • Story Points:
      0
    • 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.
    • Steps to Reproduce:
      Hide

      1) Open attached KTR/KJBs (from ESR-5160) in Spoon
      2) Point table input step of transformation to a working Oracle or MySQL database

      Show
      1) Open attached KTR/KJBs (from ESR-5160) in Spoon 2) Point table input step of transformation to a working Oracle or MySQL database

      Description

      Parent job -> intermediate job -> transformation: table input (query: SELECT 1)

      If the parent job has db transactional set to FALSE, and the intermediate job has db transactional set to TRUE, when you run the parent job it throws this error:

      2016/02/15 11:15:12 - intermediate_job - ERROR (version 5.4.0.6-154, build 1 from 2015-11-09 08.54.47 by buildguy) : !Job.Exception.ErrorHandlingJobTransaction!
      2016/02/15 11:15:12 - intermediate_job - ERROR (version 5.4.0.6-154, build 1 from 2015-11-09 08.54.47 by buildguy) : java.lang.NullPointerException
      2016/02/15 11:15:12 - intermediate_job - 	at com.pentaho.di.job.g.b(SourceFile:140)
      2016/02/15 11:15:12 - intermediate_job - 	at com.pentaho.di.job.g$1.jobFinished(SourceFile:77)
      2016/02/15 11:15:12 - intermediate_job - 	at org.pentaho.di.job.Job.fireJobFinishListeners(Job.java:614)
      2016/02/15 11:15:12 - intermediate_job - 	at org.pentaho.di.job.entries.job.JobEntryJobRunner.run(JobEntryJobRunner.java:79)
      2016/02/15 11:15:12 - intermediate_job - 	at java.lang.Thread.run(Thread.java:745)
      

      This error does not occur when the parent job is made database transactional and it runs succesfully.
      Without any changes, the intermediate job will run successfully on its own. So the error seems to only happen the intermediate job is called by the parent job.

        Attachments

        1. intermediate_job.kjb
          11 kB
        2. top_level_job.kjb
          10 kB
        3. transformation.ktr
          12 kB

          Activity

            People

            Assignee:
            AKarneichyk Alena Karneichyk (Inactive)
            Reporter:
            jbleuel Jens Bleuel
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: