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

Check if connected to repository job entry NPE when run on server

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Severity: Urgent
    • Resolution: Fixed
    • Affects Version/s: 8.2.0 GA
    • Fix Version/s: 9.0.0 GA
    • Component/s: Step
    • Labels:
    • 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:
      Tatooine (Maint)
    • Steps to Reproduce:
      Hide

      1. Connect to a repository in Spoon
      2. Create a job
      3. Add a Check if connected to repository job entry
      4. Check Specify user in the job entry and specify a user
      5. Save the job
      6. Run the job locally and the job works
      7. Run the job using the Pentaho Server run configuration, or scheduling on the server. The job fails with a NPE

      Show
      1. Connect to a repository in Spoon 2. Create a job 3. Add a Check if connected to repository job entry 4. Check Specify user in the job entry and specify a user 5. Save the job 6. Run the job locally and the job works 7. Run the job using the Pentaho Server run configuration, or scheduling on the server. The job fails with a NPE

      Description

      When using the Check if connected to repository job entry with the specify user option checked, the job entry will always fail with a null pointer exception when run on the Pentaho Server.

      2019/04/02 10:10:16 - connected-to-repo - ERROR (version 8.2.0.0-342, build 8.2.0.0-342 from 2018-11-14 10.30.55 by buildguy) : org.pentaho.di.core.exception.KettleException:
      2019/04/02 10:10:16 - connected-to-repo - Unexpected error occurred while launching entry [Check if connected to repository.0]
      2019/04/02 10:10:16 - connected-to-repo -  at org.pentaho.di.job.Job.run (Job.java:384)
      2019/04/02 10:10:16 - connected-to-repo -  at org.pentaho.di.job.Job.execute (Job.java:497)
      2019/04/02 10:10:16 - connected-to-repo -  at org.pentaho.di.job.Job.execute (Job.java:821)
      2019/04/02 10:10:16 - connected-to-repo -  at org.pentaho.di.job.Job.execute (Job.java:680)
      2019/04/02 10:10:16 - connected-to-repo -  at org.pentaho.di.job.entries.connectedtorepository.JobEntryConnectedToRepository.execute (JobEntryConnectedToRepository.java:200)
      2019/04/02 10:10:16 - connected-to-repo -
      2019/04/02 10:10:16 - connected-to-repo - 	at org.pentaho.di.job.Job.execute(Job.java:824)
      2019/04/02 10:10:16 - connected-to-repo - 	at org.pentaho.di.job.Job.execute(Job.java:497)
      2019/04/02 10:10:16 - connected-to-repo - 	at org.pentaho.di.job.Job.run(Job.java:384)
      2019/04/02 10:10:16 - connected-to-repo - Caused by: java.lang.NullPointerException
      2019/04/02 10:10:16 - connected-to-repo - 	at org.pentaho.di.job.entries.connectedtorepository.JobEntryConnectedToRepository.execute(JobEntryConnectedToRepository.java:200)
      2019/04/02 10:10:16 - connected-to-repo - 	at org.pentaho.di.job.Job.execute(Job.java:680)
      2019/04/02 10:10:16 - connected-to-repo - 	at org.pentaho.di.job.Job.execute(Job.java:821)
      2019/04/02 10:10:16 - connected-to-repo - 	... 2 more
      

        Attachments

          Activity

            People

            Assignee:
            ooliveira Octavio Oliveira
            Reporter:
            cdeptula Chris Deptula
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: