How do I modify TAC or MDM memory settings when running as a service?

Talend Version          6.x
Key words TAC as a service, MDM as a service
Product Talend Data Integration
Component Talend Administration Center
Article Type Configuration
Problem Description Memory settings in the start scripts have been changed for Tomcat and MDM, but the changes don't take effect when they are run as services on Windows.
Problem root cause  

Solution or Workaround

  1. Locate tomcat_directory/bin/tomcat8w.exe, a GUI application for monitoring and configuring Tomcat services.
  2. Rename tomcat8w.exe to the service name for TAC or MDM, which can be found in the Windows service Path to executable field, after RS//:  (to access Windows Services, type services.msc at a command prompt).

    2017-08-03 07_46_55-Screenshots.png


  3. Once the tomcat8w.exe is renamed to the service name, run it for access to launch and service settings that can be set for the Tomcat service.

  4. In the Java Options field, change the Xms and Xmx JVM memory settings as necessary:

    2017-08-03 07_50_35-Talend Administration Center 6.4.1 Properties.png


Version history
Revision #:
10 of 10
Last update:
‎10-13-2017 02:21 PM
Updated by:

To modify this setting on Unix or Linux, create the file '[TAC]/apache-tomcat/bin/' and add the 'Modified' line below. (The script will read this file if it exists.)


This file should be owned by the same user as



export JAVA_OPTS="$JAVA_OPTS -Xmx2048m -Dfile.encoding=UTF-8"


export JAVA_OPTS="$JAVA_OPTS -Xmx8192m -Dfile.encoding=UTF-8"



Then restart TAC. 


If you ran it manually, then stop (./ and re-start (./ TAC.




sh <TomcatPath>/bin/; sh <TomcatPath>/bin/



This has increased the maximum amount of memory available to the TAC process from 2GB to 8GB (the recommended amount).


The 'Java' tab here can also be used to modify the path to the Java Virtual Machine's "jvm.dll" file.


This can be a fix for when the TAC service will not start -- often after a Java upgrade, when the pre-existing Java installation directory no longer exists -- so this path needs to be updated to point to the new "jvm.dll" in the new JRE_HOME directory. (e.g. "C:\Program Files\Java\jdk1.8.0_161" instead of "C:\Program Files\Java\jdk1.8.0_144")


You should also update your JRE_HOME and JAVA_HOME system environment variables to point to the new/updated Java installation.