Getting error- JVM setup is similar to the studio while running

[Vivi2]

Hello, 
I have error message while running any job in Talend open studio Data integration 6.3.1 version.
Can you please help me if anyone knows the cause for this error? 
Error Message:
There may be some other errors caused by JVM compatibility. Make sure your JVM setup is similar to the studio.

Thanks

[Anonymous]

Check if any of the data is null at the source. Talend(Java) cannot handle null when it is expecting some value. 

use a not null filter before this step

What is the data type of rowX.fieldnameX and rowX.fieldnameY?

Do you want to add these two values or do you want to concatenate these 2 values?  

Please let me know what do you want to achieve, I can help you better

[Anonymous]

am done with the setup and am facing the below issue.

I have a scenario here in MSSQL Database.I want multiple child tables to share parent and they can generate their own ids.
I designed my job and components as attached.

On my database, i created the tables as attached

On running the above job,

I get the below error and data gets populated to parent table but not child table. Can someone help me how should i get the desired output to child table as well?

Starting job using_java at 19:05 03/07/2017.

[statistics] connecting to socket on port 4070
[statistics] connected
Incorrect syntax near ')'.
Cannot insert the value NULL into column 'ID_baby', table 'talend_local.dbo.baby'; column does not allow nulls. INSERT fails.
[ERROR]: xml_csv.using_java_0_1.using_java - tMSSqlOutput_2 - Incorrect syntax near ')'.
[ERROR]: xml_csv.using_java_0_1.using_java - tMSSqlOutput_3 - Cannot insert the value NULL into column 'ID_baby', table 'talend_local.dbo.baby'; column does not allow nulls. INSERT fails.
[statistics] disconnected
Job using_java ended at 19:05 03/07/2017. [exit code=0]

[Anonymous]

Hello everyone,

I'm also getting the same issue. Please help me to resolve this issue.

Here is the screen shots

Error message.jpg

[Anonymous]

I had the same error, but I installed the JDK and JRE again, be sure to install the last version. Delete the componets in the job and add new ones, I dont know why but it worked for me.

[Anonymous]

Hola, 

I've got the same error, but it is nothing to do with the JVM  and it is to do with the some of the coding errors in tJava and tJavaFlex components.  These kinda errors do occur in Talend.  Please do check the check the "code Viewer" tab to know the errors. 

talendJVMError.PNG

[Anonymous]

Hi,

Please help with the below error.

org.talend.designer.runprocess.ProcessorException: Job compile errors
At least job "Cass_Copy" has a compile errors, please fix and export again.
Error Line: 1797
Detail Message: The method setToNull(int) is undefined for the type BoundStatement
There may be some other errors caused by JVM compatibility. Make sure your JVM setup is similar to the studio.

[Anonymous]

Hi All,

I am getting the below error when i try to run a job in the Talend Open Studio, can you please help me to resolve this :

org.talend.designer.runprocess.ProcessorException: Job compile errors
At least job "demo01_tJava" has a compile errors, please fix and export again.
Error Line: 1
Detail Message: The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
There may be some other errors caused by JVM compatibility. Make sure your JVM setup is similar to the studio.
at org.talend.designer.runprocess.JobErrorsChecker.checkLastGenerationHasCompilationError(JobErrorsChecker.java:338)
at org.talend.designer.runprocess.DefaultRunProcessService.checkLastGenerationHasCompilationError(DefaultRunProcessService.java:510)
at org.talend.designer.runprocess.RunProcessService.checkLastGenerationHasCompilationError(RunProcessService.java:316)
at org.talend.designer.runprocess.ProcessorUtilities.generateBuildInfo(ProcessorUtilities.java:820)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:601)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:1861)
at org.talend.designer.runprocess.RunProcessContext$1.run(RunProcessContext.java:601)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:527)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:284)
at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:1190)
at org.talend.designer.runprocess.RunProcessContext.exec(RunProcessContext.java:548)
at org.talend.designer.runprocess.ui.ProcessComposite.exec(ProcessComposite.java:1401)
at org.talend.designer.runprocess.ui.views.ProcessView$RunAction.run(ProcessView.java:701)
at org.talend.designer.runprocess.ui.actions.RunProcessAction.run(RunProcessAction.java:58)
at org.talend.designer.core.debug.JobLaunchConfigurationDelegate$1.run(JobLaunchConfigurationDelegate.java:84)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.talend.rcp.intro.Application.start(Application.java:265)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
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:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)

[Anonymous]

Hello @nareshc1977 

What's JDK version are you using?

Best regards

Sabrina

[Anonymous]

Hi  @xdshi

I met the same issue with ''JVM setup is similar to the studio while running''.

I'm using JDK1.8.0_202 on Win10 64bit system. Thanks.

BR,

20190326175646.png

[Anonymous]

Hello @HarveyLiu 

Does this JVM setting issue repro on all your jobs or a specific one?

Best regards

Sabrina