TOS: All jobs failing to build (java.lang.NullPointerException Error)

[MPT]

This issue concerns our installation of Talend Open Studio for Data integration 7.3.1.20200219_1130.

We have 5 projects of different sizes and the issue concerns our biggest project, with 50 or so jobs. Every single begun to fail like the example below. We did not observe any behavior prior to this that would have suggested something is wrong. One moment the developer was developing and executing the job in Studio and suddenly the job they were working on did not execute. Then we tried other jobs and those did not run either. We can't even build and deploy jobs from this project anymore, the same exception prevents building jobs.

This does not affect our other projects, jobs in those work, execute and deploy.

We're currently comparing project setup and metadata and configuration files between working project and this non-working project hoping to find a way fix the project instead of rebuilding it. Often the proposed solution for this types of issues is to make a new project and import jobs there. We're hesitant to do that yet as then we would not know what was the root cause for this issue and also, we've never done that before so we don't know how well importing 50 jobs with linked code, schemas and contexts would all go correct in the first try and work.

 

java.lang.NullPointerException

at org.talend.designer.runprocess.JobErrorsChecker.checkRoutinesCompilationError(JobErrorsChecker.java:424)

at org.talend.designer.runprocess.JobErrorsChecker.checkLastGenerationHasCompilationError(JobErrorsChecker.java:373)

at org.talend.designer.runprocess.DefaultRunProcessService.checkLastGenerationHasCompilationError(DefaultRunProcessService.java:539)

at org.talend.designer.runprocess.RunProcessService.checkLastGenerationHasCompilationError(RunProcessService.java:317)

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

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

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(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

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)

[MPT]

Additional information:

We have been able to pinpoint the time of corruption to a specific time.

Before Wednesday 4pm, folder "\<project workspace>\<project>\.metadata\.plugins\org.eclipse.core.resources\.projects" was almost empty. There was really nothing there. After 4pm Wednesday, for every job we tried to build, a corresponding directory begun forming into this folder. We have no idea why Studio begun creating these directories under "org.eclipse.core.resources\.projects" but it is related to this issue.

 

[Anonymous]

Hello,

Could you please let us know what's JDK version are you using in your talend open studio 7.3.1.20200219_1130? Was your Job working fine in a previous version of TOS?

Please make sure that you point it to the JDK folder instead of JRE folder under Talend Window -> Preferences - > Java -> Installed JREs

Best regards

Sabrina

[Anonymous]

If you have 5 projects and only 1 has seen these issues, I suspect that this could be caused by your project backup/export. Can you try this again and ensure that you have absolutely everything included in the export. I presume that you carried out the standard export and import as well?

[MPT]

We don't have a systematic backup set up for Talend. For Talend machines we have a vm snapshot taken daily at 6pm and that is the only restore point for us.

These jobs worked day before yesterday and begun failing after ~4pm and there were no backups, or exports or imports done then. The only actions performed on Talend machines were launching project, editing job, executing job within studio and exiting project, launching project again etc.

For reference, we have two machines, TEST and PROD. We build jobs on TEST machine, then export to PROD, import to studio, review and deploy. The broken project is in our TEST machine.

[MPT]

Additional information:

*updated*

We created a new *workspace* and a new project and imported all jobs and related schemas etc. there. This fixed the issue so that jobs execute and deploy again in test. We're still keeping the broken project and investigating what might be the root cause there.

[Anonymous]

OK, this sounds like it may have been caused by a broken project folder. This could also have been caused by a broken Workspace folder. My next suggestion was going to be to export your content and create a new Workspace folder to attempt to resolve this.

[MPT]

I haven't had a chance to check the broken project yet, but we created a new project and imported the jobs there from the broken project and everything worked there, thank goodness. I then checked the new project and "Installed JREs" is pointing to JRE 1.8.0.301 there, not JDK. Since we haven't touched the java settings for many many months, I strongly expect the broken project to also point to the same JRE.

[jlolling]

I know this issue. And yes, your way is currently the only way to fix it.