
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Java Runtime Environment Native memory allocation (mmap) failed to map bytes for committing reserved memory
Hi,
I've got a job which runs fine on my local machine, but when i try and run in the cloud i get the error message below. It looks like it's trying to allocate more memory that is available on the EC2 box (16Gb). How do i set the jvm settings for a job published to TMC?
I have tried unticking use specific jvm arguments in each job.
Thanks
# # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (mmap) failed to map 2914516992 bytes for committing reserved memory. # An error report file with more information is saved as: # /opt/Talend-RemoteEngine-V2.4.0/TalendJobServersFiles/repository/MAIN_PROJECT_run_plan_yield_report_5e67a705efe3a6334692a53f_8.16/run_plan_yield_report/hs_err_pid7059.log OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000542800000, 2914516992, 0) failed; error='Cannot allocate memory' (errno=12) ### Job ENDED WITH ERROR at 2020/04/07 12:08:14 (jobId=5e67a705efe3a6334692a53f_8.16, jobExecutionId=20200407120511_uWVWu) ###
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was fixed by lowering the VM arguments to
-Xms1024M
-Xmx4096M
In both
Preferences>Talend>Run/Debug
and also in the job in the advanced setting in the run tab

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://www.talend.com/blog/2018/08/13/going-serverless-with-talend-through-ci-cd-and-containers/

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks but i don't think that is quite the answer.
To be clear we have dozens of other jobs deployed and running everyday in TMC but just this job seems to error and I'm not sure what i've done differently or how to fix it.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was fixed by lowering the VM arguments to
-Xms1024M
-Xmx4096M
In both
Preferences>Talend>Run/Debug
and also in the job in the advanced setting in the run tab
