Talend throwing "Exception in thread "main" java.lang.Error: Unresolved compilation problem:"

[Anonymous]

I have been having intermittent problems with Talend (6.4.1 on Windows 10) throwing this error.  I was having problems a couple of days ago and so, following the guidance some things I found by searching, I set the JAVA_HOME environment variable to  C:\Program Files\Java\jdk1.8.0_151\bin\javaw.exe and also set a value of -vm C:\Program Files\Java\jdk1.8.0_151\bin\javaw.exe in eclipse.ini.  This seemed to fix the problem this morning. Now this afternoon I am getting this error again.  I haven't changed anything about the jobs where I am getting the errors.  What is going on?  Where do I even begin to start looking?

A few other things things that I have read in other posts. 

1. I am running the job from the designer just as earlier this morning when all of this was working. 
2. I have tried a clean install of TOS and then setting up a simple job as suggested in this post.  That is still giving the same error.
3. The installation path for my main installation is C:\Talend\TOS_DI-20170623_1246-V6.4.1, the workspace path for this copy is E:\Brian MacDonald\Documents\Data_Integration\Talend\workspace (note the space)
4. The installation path for my "clean install" version is C:\TOS\TOS_DI-20170623_1246-V6.4.1 and the workspace path for this version is C:\TOS\TOS_DI-20170623_1246-V6.4.1\workspace (the default - no spaces)

Any help would be appreciated.

[Anonymous · Accepted solution]

So this what appears to have worked for me.

I had a couple of different Java versions installed on my system.  So first I uninstalled them all. Then I reinstalled the one i wanted to use (which in my case is 8.0_151).

Then:

1. Goto Preferences >> Java >> Installed JRE's
2. Click Add and browse to \Program Files\Java\jdk1.8.0_151
   1. In my case the "Location" variable for the jre did not change but the "Name" variable for the jre in this dialog box did.  I am not sure the impact of this but it is the only thing that appears to have changed.  Who knows, maybe "refreshing" this variable is the key.
3. Click OK and then set the newly added jre as the default.  
4. Click OK, say a small prayer and run a job.

Note that it appears I will have to do these steps for all projects.  I made this fix and it worked for a job that was throwing an error.  Then I switched projects and got the error again.  I did steps 1-4 in the new project and all was good.

[Anonymous]

Hello,

Thanks for sharing your use case with us on forum. And ensure your JDK bin is included in your PATH environment variable and is being reached.

Best regards

Sabrina

[KB_Parpally]

Thanks a lot BRM, *****
It Solved my Issue

[Anonymous]

Hi, there,

I am unable to do above settings and facing the same error in a tMap logic. Can you help me out in solving it.

[Anonymous]

This seems like a different cause of the problem than what this thread aims to solve.  I suppose I would start by testing each of the condition statements individually to see if they work before combining them into a series like you have. Also, for complex logic like this you might also look into tJavaRow.  tJavaRow allows "real" java and so is easier to code these complex logic statements.

Hope that helps.

[jeoste]

I just changed my JRE to JDK and it worked ; for an obscur reason, my JRE looks like corrupted and I cannot compile / execute my code.

[Anonymous]

Hello,

JDK is not needed to run job especially in the studio, but needed to export the job.

Best regards

Sabrina