Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
MUEXTERM
Contributor
Contributor

java.lang.NullPointerException in talend 7.3.1 after executing a JoB

Hello everyone,

>>> I'm having a curious issue with talend 7.3.1 :

org.talend.designer.runprocess.ProcessorException: java.lang.NullPointerException.

Thanks to you all in advance for your help.

>>> Configurations:

  • Talend Data integration version

    7.3.1

  • OS : Win10 version 21H2

  • java version 1.8.0_202
  • I have a set of multiple Parent Job not linked together
  • each Parent job has different number of subjobs

>>> Scenario :

  • After starting my talend IDE, when I run a job, it runs successfully without any issue
  • when I run the same job after the previous successful run, it does not run and yield and error
  • when I try to run another Job parent or child job, it still does not run and yields the same error
  • to run it, i have to restart the IDE completely
  • and the same error happens over and over again

>>> This what I get as error:

0695b00000lxpo3AAA.png

>>> Here is the complete error log:

org.talend.designer.runprocess.ProcessorException: java.lang.NullPointerException

at org.talend.designer.runprocess.ProcessorUtilities.generateBuildInfo(ProcessorUtilities.java:947)

at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:1309)

at org.talend.designer.runprocess.ProcessorUtilities.generateNodeInfo(ProcessorUtilities.java:1650)

at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:1257)

at org.talend.designer.runprocess.ProcessorUtilities.generateNodeInfo(ProcessorUtilities.java:1650)

at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:576)

at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:2068)

at org.talend.designer.runprocess.RunProcessContext$1.run(RunProcessContext.java:601)

at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:440)

at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:356)

at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:474)

at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:240)

at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:966)

at org.talend.designer.runprocess.RunProcessContext.exec(RunProcessContext.java:548)

at org.talend.designer.runprocess.ui.ProcessComposite.exec(ProcessComposite.java:1448)

at org.talend.designer.runprocess.ui.views.ProcessView$RunAction.run(ProcessView.java:700)

at org.talend.designer.runprocess.ui.actions.RunProcessAction.run(RunProcessAction.java:63)

at org.talend.designer.core.debug.JobLaunchConfigurationDelegate$1$1.run(JobLaunchConfigurationDelegate.java:98)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3919)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3550)

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)

at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)

at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)

at org.talend.rcp.intro.Application.start(Application.java:280)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)

at org.eclipse.equinox.launcher.Main.run(Main.java:1501)

Caused by: java.lang.NullPointerException

at org.talend.designer.maven.tools.BuildCacheManager.isJobBuild(BuildCacheManager.java:113)

at org.talend.designer.runprocess.maven.MavenJavaProcessor.build(MavenJavaProcessor.java:390)

at org.talend.designer.runprocess.ProcessorUtilities.generateBuildInfo(ProcessorUtilities.java:944)

... 42 more

Labels (3)
7 Replies
Anonymous
Not applicable

Hello,

We need a little bit more information to address your issue.

Are you using talend data integration subscription solution?

Any patch installed? Is Studio using project from a branch or master branch you selected to login? Does this issue occur even in a new local project?

Thanks for your time!

Best regards

Sabrina

 

 

MUEXTERM
Contributor
Contributor
Author

Hello,

I'm not using a talend data integration subscription.

I'm using the community edition on a local machine.

There no branch at all.

It also occurs on a new project.

Thanks for your help.

 

Best regards.

Anonymous
Not applicable

Hello,

Does Talend Studio start as normal? No problem with the jdk/jre(set the Java home path correctly)?

It seems to be the corruption of Workspace directory. My next suggestion was going to be to export your content and create a new Workspace folder to attempt to resolve this.

Best regards

Sabrina

 

MUEXTERM
Contributor
Contributor
Author

Hello,

 

Talend Studio does start normallly.

 

The Jkd/jre is set correctly with an appropriate Java home path.

 

I have also switch/create workspaces several times.

 

FYI: I have talend Studio 6.4 installed on my computer with different directories that works properly without the actual errors on TOS 7.3.1

 

0695b00000ly6N4AAI.png0695b00000ly6NJAAY.png 

Anonymous
Not applicable

Hello,

What's your installation path for v 7.3.1? Are there some blank space in your path or typo in PATH variable?

Is it OK with you to reinstall your studio 7.3.1 to see if it is working well?

Best regards

Sabrina

MUEXTERM
Contributor
Contributor
Author

Hello,

installation path for V7.3.1 : C:\SVN\dhe2\talendProjects_ws\TAP_BIZZ

there ane no blank spaces

I have done 2 reinstallation already.

 

Best regards

 

Anonymous
Not applicable

Hello,

I will make an investigation with my team to try to find out the root cause and then come back to you as soon as we can.

Best regards

Sabrina