JAVA heap space error

Anonymous — Sat, 11 May 2019 10:57:12 GMT

Hi all,

I am working on Talend for 2 years now in Paris.

At the beginning I had a 2 days training about how to make a job, run a job.... only beginner stuffs.

All the rest is self discovering

So sorry in advance for my questions

I am trying to understand why I am facing this error. I guess that is about JVM and memory.

Xms:128 (I read that is the minimum of memory)

Xmx:4096 (I read that is the maximum of memory)

The jobserver has 16go of memory so I guess I can not increase more and there are others jobs / project using this server atthe same time

My job is around 12 millions rows with 10 columns

tJDBCInput (with a bit complex query) <-> tJCBDOutput (full refresh)

I do not understand where in this job the memory is using. Is it when the result of the query is sent to Talend?

And other issue is that in my firm we are using a scheduling tools and the exit code is 0.

The job looks like is running correctly but in fact there is an java heap space error in the log file.

So how to force the job to die? Do I have a tDie link to tJDBCInput and tJDBCOuput?

I did manage to avoid the java heap space error by splitting the query in mulitples queries but it was OK for few days and now the java heap is back

By example

year = 2015 tJDBCInput (with a bit complex query) <-> tJCBDOutput (full refresh)

if subject ok then

year = 2016 tJDBCInput (with a bit complex query) <-> tJCBDOutput (Append)

if subject ok then

year = 2017 tJDBCInput (with a bit complex query) <-> tJCBDOutput (Append)

Thank you all in advance for your help.

Re: JAVA heap space error

David_Beaty — Sat, 11 May 2019 12:59:20 GMT

Hi,

Can you share a screenshot of the job design?

Anonymous — Sat, 11 May 2019 13:35:32 GMT

Hi David,

Sure very simple job

tJDBCOutput

Job advanced parameters

Thanks for you help

David_Beaty — Sat, 11 May 2019 17:46:28 GMT

Hi,

if you can run the job locally within Studio, run something like VisualVM and see when it starts consuming the memory.

Something looks a bit odd thar you have 2 “If” connections coming together at the tJava.