Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Write Table now available in Qlik Cloud Analytics: Read Blog
cancel
Showing results for 
Search instead for 
Did you mean: 
KamilG
Contributor
Contributor

Error when I try to run job

When I try to run job locally I got error: 

Cannot invoke "org.talend.core.runtime.process.ITalendProcessJavaProject.getJavaProject()" because "talendCodeJavaProject" is null

Log: 

java.lang.NullPointerException: Cannot invoke "org.talend.core.runtime.process.ITalendProcessJavaProject.getJavaProject()" because "talendCodeJavaProject" is null
at org.talend.designer.runprocess.java.TalendJavaProjectManager.getTalendCodeJavaProject(TalendJavaProjectManager.java:241)
at org.talend.designer.runprocess.java.TalendJavaProjectManager.getTalendCodeJavaProject(TalendJavaProjectManager.java:206)
at org.talend.designer.runprocess.DefaultRunProcessService.getTalendCodeJavaProject(DefaultRunProcessService.java:777)
at org.talend.designer.runprocess.RunProcessService.getTalendCodeJavaProject(RunProcessService.java:426)
at org.talend.designer.codegen.AbstractRoutineSynchronizer.getAll(AbstractRoutineSynchronizer.java:87)
at org.talend.designer.codegen.AbstractRoutineSynchronizer.getRoutines(AbstractRoutineSynchronizer.java:73)
at org.talend.designer.codegen.JavaRoutineSynchronizer.syncAllRoutines(JavaRoutineSynchronizer.java:57)
at org.talend.core.model.repository.RepositoryManager.syncRoutineAndJoblet(RepositoryManager.java:89)
at org.talend.designer.runprocess.ProcessorUtilities.updateCodeSources(ProcessorUtilities.java:2038)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:2112)
at org.talend.designer.runprocess.RunProcessContext$2.run(RunProcessContext.java:679)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:436)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:352)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:470)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:230)
at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:999)
at org.talend.designer.runprocess.RunProcessContext.exec(RunProcessContext.java:626)
at org.talend.designer.runprocess.remote.RunRemoteProcessContext.exec(RunRemoteProcessContext.java:89)
at org.talend.designer.runprocess.ui.ProcessComposite.exec(ProcessComposite.java:1471)
at org.talend.designer.runprocess.ui.views.ProcessView$RunAction.run(ProcessView.java:751)
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:132)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4046)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3662)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:342)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:648)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:342)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:173)
at org.talend.rcp.intro.Application.start(Application.java:320)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:208)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:651)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:588)
at org.eclipse.equinox.launcher.Main.run(Main.java:1459)
at org.eclipse.equinox.launcher.Main.main(Main.java:1432)

 

 

Labels (3)
1 Solution

Accepted Solutions
marksouzacosta

Hi @KamilG,

We'll need more information about your Job, Talend Studio version and how are you running the job, etc. So far, this is what I got from ChatGPT:

This error in Talend Studio:

Cannot invoke "org.talend.core.runtime.process.ITalendProcessJavaProject.getJavaProject()" because "talendCodeJavaProject" is null

...typically means Talend's internal Java project structure is corrupted or not properly initialized.

Most common causes:

  1. Corrupted workspace or project cache.
  2. Missing or broken code/routine synchronization.
  3. Misconfigured Java environment or path.
  4. Failed routine generation or job compile step.

Recommended Fixes (Step-by-Step) 🔁 1. Force regenerate project Java code

This often fixes the null pointer issue.

  • Go to Project Settings > Build > Java > Rebuild Project
  • Or right-click on your job or routines and select Build or Rebuild.

Alternatively:

  • From the menu:
    Project > Clean All... > check Delete old code folders > OK.

🔄 2. Refresh Talend Project

Sometimes metadata is out-of-sync.

  • Right-click your project name in the Repository panel
  • Select "Refresh"
  • Then try "Rebuild Project" again

🧹 3. Clear and regenerate the Talend Java Project

  1. Close Talend Studio.
  2. Go to your Talend workspace folder, delete the following (backup first if needed):
<YourWorkspace>\.Java\src
<YourWorkspace>\.Java\lib
<YourWorkspace>\.Java\target
<YourWorkspace>\.Java\.settings
  1. Reopen Talend Studio.
  2. In Talend Studio:
    Project > Clean All > OK

🧰 4. Check Java Version & Path

Make sure your system uses Java 17, and there's no override (like _JAVA_OPTIONS) pointing to something else.

Check by running in Command Prompt:

java -version

Should return something like:

openjdk version "17.0.x"

If not, update your JAVA_HOME and Path environment variables.


🛠 5. Check for custom routines or invalid scripts

If you recently edited or imported a routine, joblet, or custom code, try:

  • Disabling/removing the latest custom routine
  • Then clean & rebuild

🚨 6. Last Resort: Create a new workspace

If nothing else works:

  1. Open Talend Studio
  2. Choose File > Switch Workspace > Other…
  3. Create/select a new workspace
  4. Import your existing project into it

Let me know what worked or if you'd like help checking your talend-studio-win-x86_64.ini or environment variables too.

Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

View solution in original post

1 Reply
marksouzacosta

Hi @KamilG,

We'll need more information about your Job, Talend Studio version and how are you running the job, etc. So far, this is what I got from ChatGPT:

This error in Talend Studio:

Cannot invoke "org.talend.core.runtime.process.ITalendProcessJavaProject.getJavaProject()" because "talendCodeJavaProject" is null

...typically means Talend's internal Java project structure is corrupted or not properly initialized.

Most common causes:

  1. Corrupted workspace or project cache.
  2. Missing or broken code/routine synchronization.
  3. Misconfigured Java environment or path.
  4. Failed routine generation or job compile step.

Recommended Fixes (Step-by-Step) 🔁 1. Force regenerate project Java code

This often fixes the null pointer issue.

  • Go to Project Settings > Build > Java > Rebuild Project
  • Or right-click on your job or routines and select Build or Rebuild.

Alternatively:

  • From the menu:
    Project > Clean All... > check Delete old code folders > OK.

🔄 2. Refresh Talend Project

Sometimes metadata is out-of-sync.

  • Right-click your project name in the Repository panel
  • Select "Refresh"
  • Then try "Rebuild Project" again

🧹 3. Clear and regenerate the Talend Java Project

  1. Close Talend Studio.
  2. Go to your Talend workspace folder, delete the following (backup first if needed):
<YourWorkspace>\.Java\src
<YourWorkspace>\.Java\lib
<YourWorkspace>\.Java\target
<YourWorkspace>\.Java\.settings
  1. Reopen Talend Studio.
  2. In Talend Studio:
    Project > Clean All > OK

🧰 4. Check Java Version & Path

Make sure your system uses Java 17, and there's no override (like _JAVA_OPTIONS) pointing to something else.

Check by running in Command Prompt:

java -version

Should return something like:

openjdk version "17.0.x"

If not, update your JAVA_HOME and Path environment variables.


🛠 5. Check for custom routines or invalid scripts

If you recently edited or imported a routine, joblet, or custom code, try:

  • Disabling/removing the latest custom routine
  • Then clean & rebuild

🚨 6. Last Resort: Create a new workspace

If nothing else works:

  1. Open Talend Studio
  2. Choose File > Switch Workspace > Other…
  3. Create/select a new workspace
  4. Import your existing project into it

Let me know what worked or if you'd like help checking your talend-studio-win-x86_64.ini or environment variables too.

Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com