I need to run a talend job with java 32 bit, because of loading a native code. I change the java version under preference/java/installed jre, but if I run the job under talend studio, it starts the 64 bit Version.
How can I change that talend Studio run the job with 32 bit?
when you Install talend you will see two talend versions in the installed folder. one with x86 which is 32 bit version of talend and another exe file with x86_64.exe prefix. Try starting x86 version of the studio and run the job and see if anything helps. I have attached images of both versions of the talend which I mentioned.
no the same problem. I start Talend-Studio-win32-x86.exe and he say the same error: Can't load IA 32-bit .dll on a AMD 64-bit platform
Could you please type java -version in cmd to see if you are on 64 bit JDK or 32 bit. It seems that you are still using jdk 64 bit. Make sure that you have installed 32 bit JDK in your machine so that you can use 32 bit platform to read 32-bit .dll. not 64 bit.
-d32 is added into JVM setting to tell studio to use 32 bit platform to read 32-bit .dll.
I got this error: Error: This Java instance does not support a 32-bit JVM.
yes my java_home is link to 64 bit. I dont want to change that. In Eclipse I can set which version he choose for running.
no I am changing the java home path to 32 bit version....but the same error. If I use -version arguments:
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
where this parameter is configurated?
In my case, I only have TOS_DI-win-x86_64.exe as an option. Does this mean that Talend Open Studio can only run on a 64 bit machine? I'm chained to a 32-bit virtual machine and would like to use Talend, but do not know how to make it run. Thanks!
TOS_DI-win-x86_64.exe is used for 64 bit OS and 64 bit JDK. Do you have TOS_DI-win32-x86.exe file in your installation path? Which is talend build version you are using?
Unfortunately, I don't have a TOS_DI-win32-x86.exe. My build is 220.127.116.1180116_1512. At least I think that is the build number. Worst case I can move data to a 64-bit machine, but that can be painful. We are talking about millions of records and several gigs...