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

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] Could not create the Java virtual machine.

Hello,
I install TOS v2.4 on Vista with TalendOpenStudio-win32-x86.in file :
-vmargs
-Xms500m
-Xmx500m
-XX0683p000009MAB6.pngermSize=128m
-XX:MaxPermSize=128m
I can start TOS and create job, but when I run a job (even a simple job like tRowGenerator => tLogRow), I get the message:
Starting job simple at 17:21 26/06/2008.
Could not create the Java virtual machine.
Error occurred during initialization of VM
Could not reserve enough space for object heap
Job simple ended at 17:21 26/06/2008.
Remark: I can run the job in debug mode.
Thanks.

Labels (3)
27 Replies
Anonymous
Not applicable
Author

Hello kevins
As Vincenzo vitale said, try to move the JAVA_HOME/bin entry in the Path variable to the first position should solve the problem.
Best regards
shong
Anonymous
Not applicable
Author

it already was.
Anonymous
Not applicable
Author

The problem is that the JVM cannot reserve the space.
The ini memory settings are only for Talend, not for the running job. You need to set those in the Preferences under Talend->Run and Debug, which, by default is set to Xmx 1024.
Try decreasing the memory setting in the Preferences and run it again. If that doesn't work, export the job as a script and try running it outside of the Studio via the Command Prompt.
Anonymous
Not applicable
Author

Jandy,
thanks, that allowed the job to run fine.
Anonymous
Not applicable
Author

Hi,
I am running TIS version 3.2.1 and have tried many combinations of the memory setting but still get :-
Could not create the Java virtual machine.
Error occurred during initialization of VM
Could not reserve enough space for object heap
I have 2.5Gb of memory.
Current settings are :-
-vmargs
-Xms256M
-Xmx1536M
-XX:MaxPermSize=128m
I want to be able to run the debugger, so exporting the job and running from the command line is not feasible.
One of the posts says :-
'Moving the JAVA_HOME/bin entry in the Path variable to the first position should solve the problem.'
but I do not know how to do this??
Can anyone help?
Anonymous
Not applicable
Author

If your OS is Windows, Windows itself will always reserve HALF of all available memory for itself, leaving the other half for all applications. This means you may have significantly less memory available for the JVM than you might think.
Anonymous
Not applicable
Author

I have the same issue since some days : I can't launch the jobs that I create, but I can launch those already created...
Windows XP
Talend Open Studio 3.2.1.r31371
-Xms1024M
-Xmx2048M
- Java : jre6
_AnonymousUser
Specialist III
Specialist III

i have the same problem
Windows XP
Talend Open Studio4.0
RAM 1.75 GO
- Java : jre6
I have chaged -Xms 256 to 500
and -Xmx1024M to -Xmx2048M
but it doesn't work !!!
any ideas !!!
_AnonymousUser
Specialist III
Specialist III

Same issue, but I am pretty sure it is purely down to the fact that the max ammount that you tried to reserve is not actually available to the JVM. This did not work: "-Xms256m -Xmx1024m" but when I changed it to "-Xms256m -Xmx512m" that was fine (I used the -XX:+UseParallelGC garbage collector)
Try gradually reducing the Xms and Xmx and see what happens
Anonymous
Not applicable
Author

I have the same issue since some days : I can't launch the jobs that I create, but I can launch those already created...

It was the project properties who were incorrect, I change them to ""-Xms256m -Xmx1024m" and I can now create job without any problem.