You are not logged in.
I found how to fix -Xms and -Xmx parameters to get them into .bat .sh when Exporting script job files.
You have to set them on the Run tab (the tab that is activated while you run your program from Talend IDE - where there's the console output screen) and then go to "JVM arguments" left tab (see configuringJVMargumentsPerJob.png). You have to do that for each job a part from setting it on "Windows - Preferences... - Run / Debug" menu.
Hope it helps!
In your case, it is not even able to initialize the JVM using the Xms parameter. Make sure you are entering the correct syntax for those parameters, and that you have enough space to be reserved for the smallest threshold. (Keep in mind that the syntax is case-sensitive).
Here is an interesting link showing six common mistakes in setting the java heap space:
http://javahowto.blogspot.com/2006/06/6 … -heap.html
Hi, I get that error when I run my job:
Could not create the Java virtual machine
Error ocurred during initialization of VM
Could not reserve enough space for object heap
However, if I export that job to a .bat file, edit its contents and I remove the -Xms256M and -Xmx1024M options it runs right!
What happens if I remove those options? I'm fed up of trying several values for -Xms and -Xmx and none make it work. It just works if I remove these options.
PS: My job is very simple! Just a tFixedFlow and a tFileOutputDelimited
It works at last.
It was resolve in 2.4.4.
i don't know for the v3. To be tested
I'm working with TOS 3.0.0 and i'm experiencing the same problem : the cursor option in component tPostgresIntput seems not to work (i got a lack of memory error and changing the cursor size seems not chnaging anything)
Do you have some news about that problem ? Did the latest release (3.0.2) solve the problem ?
still not working in 3.0.0
I've the same problem on Talend 2.3.3 and 2.4.1.
The "cursor limit" on a tPostgreSQLInput doesn't resolve the problem for me.
I try to select 12 millions rows but the jobs die by java heap space.
Still not working in 3.0.0M1
Still not working in 2.4.1
Is this cursor really work or not ?
In 2.4.0, you have no more reason to use a tJDBC since the postgres jdbc driver have been updated in [Bugtracker] bug 4051
Thats why you should be able to use tPostGresInput with cursor.
I have to make some new tests on the question asked by Chris Doudet : is the cursor really working in 2.4 with Postgres.
I come back to you.
I think like you but if I must use a tJDBCIput, I can't read more than 2 500 000 lines, isn't it ?
normally the cursor is here for this kind of thing.
i think it's a BUG not a limitation,
talend team, can you confirm ?
thanks for your answer.
I tried the same thing, and I have the same problem. So I asked me if I am alone in this case or not ? And if I did a wrong thing in my job ? :-)
I conclude TOS in not capable to read around more than 2 500 000 lines. I think TIS can do that but I don't use TIS so... Somebody has the answer ?
i use 2.4.0 and i try cursor (1000) on a 3 000 000 row : failed.
just a tpostgres to a tfileoutputdelimited.