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

NPE when running looping transformation - at org.pentaho.di.core.gui.JobTracker.getJobTracker(JobTracker.java:125)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Severity: Urgent
    • Resolution: Fixed
    • Affects Version/s: 5.2.0 GA
    • Fix Version/s: 6.0.0 GA
    • Component/s: Job
    • Labels:
      None
    • Environment:
      16 GB of RAM on machine, xmx 4096m, 256 on application
    • 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.
    • Sprint Team:
      Maintenance
    • Operating System/s:
      Windows Server 2008 R2 (64-bit)

      Description

      I have a Job that's:

      Step 1) Running a Transformation that processes about 20,000 rows x 30 columns and stores the results in memory
      Step 2) Running a looping Transformation that reads the rows from memory and then writes each of those rows one by one (Execute for each row) into an output .csv file. The filename dynamically generated using parameters

      I randomly encounter a Java NullPointerException somewhere along the way of Step 2 which causes Spoon to crash.

      I am unable to characterize the issue. It doesn't have anything to do with the dataset. It crashes at absolutely random points during execution, and every so often, it executes all of it successfully.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              dmukherji Dev Mukherji
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0h
                  0h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 11h
                  11h