Increasing CA TDM Portal JVM memory

Document ID : KB000010602
Last Modified Date : 14/02/2018
Show Technical Document Details

The server running TDM Portal has a lot of memory available. This article will describe how to increase the amount that gets allocated to TDM Portal to ensure effective use of resources and gain better performance.


TDM Portal is based on Tomcat which is ultimately a Java process. The Java Run-time Environment (JRE) sets the Initial and Maximum heap size based on the total amount of physical memory the system has. For a Server based OS, this is generally 1/64th of total physical for Initial and 1/4th of total physical for Maximum. On a system with 16 Gigs of RAM, this would equate to 256 Megs and 4 Gigs respectively.


The TDM Portal service uses the "Java Service Wrapper" in order to start the Java process on Windows.

The wrapper.conf file contains configuration options for Initial and Maximum memory which can be modified.

The default location of this file is: C:\Program Files\CA\CA Test Data Manager Portal\service\conf\wrapper.conf

The values need to be un-commented and changed to the desired values:

# Initial Java Heap Size (in MB)

# Maximum Java Heap Size (in MB)


The example above, (using the same 16 Gig server) would change the initial value from 256 Megs to 3 Gigs and the Max value from 4 Gigs to 6 Gigs.


Once the file has been modified, save it and recycle the "CA Test Data Manager Portal" service.

Additional Information:

You can validate the Initial and Max Heap sizes using the "jinfo" command. This is shipped with the Java Development Kit (JDK).

jinfo -flag InitialHeapSize [PID]

jinfo -flag MaxHeapSize [PID]

Note: The jinfo command works best when the versions of the JDK and JRE are properly matched. You can confirm the java version used by TDM Portal by running the following command:

"C:\Program Files\CA\CA Test Data Manager Portal\jre\bin\java.exe" -version


"Java Service Wrapper" Documentation for the above referenced properties.